Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 721ede62b0ad7c9c1511622b479fd7db4ccda6340767a2463299283bf33ddb43

Tx prefix hash: 2b7df5384e6911873494504c793d155330ce7f04b27326348ffc7ec41f47b7cd
Tx public key: 15a070b3fbcb7f13ce6d95221c80a824c2a5adaae949aca25bab313fc8a9cab7
Timestamp: 1703021599 Timestamp [UCT]: 2023-12-19 21:33:19 Age [y:d:h:m:s]: 01:151:04:29:48
Block: 916805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369188 RingCT/type: yes/0
Extra: 0115a070b3fbcb7f13ce6d95221c80a824c2a5adaae949aca25bab313fc8a9cab7021100000003e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5ca930eb1a8f5c013163d9dc7d4f52b3284b42f2d31e00eeff585768c33b898 0.600000000000 1374365 of 15

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": 916815, "vin": [ { "gen": { "height": 916805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5ca930eb1a8f5c013163d9dc7d4f52b3284b42f2d31e00eeff585768c33b898" } } ], "extra": [ 1, 21, 160, 112, 179, 251, 203, 127, 19, 206, 109, 149, 34, 28, 128, 168, 36, 194, 165, 173, 170, 233, 73, 172, 162, 91, 171, 49, 63, 200, 169, 202, 183, 2, 17, 0, 0, 0, 3, 228, 187, 107, 131, 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