Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23daf9472b8a785654d76c4e2c9a72ac31d907eaf35f12f0b541b10082c77c43

Tx prefix hash: 2b948bf1a60ce04a41398702a869cee674503f2aa967d65188293a1c583894f7
Tx public key: e0d1558322b5df8fc25726d66f3f6a953f68eaf6d0ffe3d61a052e105fdf6030
Timestamp: 1577713871 Timestamp [UCT]: 2019-12-30 13:51:11 Age [y:d:h:m:s]: 04:333:11:45:20
Block: 35069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1127436 RingCT/type: yes/0
Extra: 01e0d1558322b5df8fc25726d66f3f6a953f68eaf6d0ffe3d61a052e105fdf60300211000000088a2ee0d9000000000000000000

1 output(s) for total of 469.680684202000 dcy

stealth address amount amount idx
00: aa0c39f86b07ee1ecda01019b8ebbc5fa91c07b454999d6e91d17bb9d24b19b5 469.680684202000 59072 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": 35079, "vin": [ { "gen": { "height": 35069 } } ], "vout": [ { "amount": 469680684202, "target": { "key": "aa0c39f86b07ee1ecda01019b8ebbc5fa91c07b454999d6e91d17bb9d24b19b5" } } ], "extra": [ 1, 224, 209, 85, 131, 34, 181, 223, 143, 194, 87, 38, 214, 111, 63, 106, 149, 63, 104, 234, 246, 208, 255, 227, 214, 26, 5, 46, 16, 95, 223, 96, 48, 2, 17, 0, 0, 0, 8, 138, 46, 224, 217, 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