Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 9bb8de945d0ae64f380b4829add7b7cde2965d60fb5241f23c5bbaa96e46b1dc

Tx prefix hash: 795029ad678ca0f1f22071604dd1b7984b5d3c19df5919152ce7e13c68e6e82e
Tx public key: a025b013f5185d8611b83c7d98e9583416a6a1ac185be0a1897d7af963f22584
Timestamp: 1649861149 Timestamp [UCT]: 2022-04-13 14:45:49 Age [y:d:h:m:s]: 03:202:01:21:06
Block: 479359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 922680 RingCT/type: yes/0
Extra: 01a025b013f5185d8611b83c7d98e9583416a6a1ac185be0a1897d7af963f225840211000000012e6b1fd5000000000000000000

1 output(s) for total of 15.842326163000 dcy

stealth address amount amount idx
00: f0c3a0f2b62e00a5d969e069e8366bd507521db0e2c1f4366268a218ffd29904 15.842326163000 900230 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 479369, "vin": [ { "gen": { "height": 479359 } } ], "vout": [ { "amount": 15842326163, "target": { "key": "f0c3a0f2b62e00a5d969e069e8366bd507521db0e2c1f4366268a218ffd29904" } } ], "extra": [ 1, 160, 37, 176, 19, 245, 24, 93, 134, 17, 184, 60, 125, 152, 233, 88, 52, 22, 166, 161, 172, 24, 91, 224, 161, 137, 125, 122, 249, 99, 242, 37, 132, 2, 17, 0, 0, 0, 1, 46, 107, 31, 213, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8