Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bab97cdb83697357f5a3ee26597900d6bcdcc7685b2961699ba13fe5fad81627

Tx prefix hash: 1a755b9f9a82e48e9398d35636f2d9c4439bd440a19d04d5c9328224f78f8692
Tx public key: e2451efca5e30cac14cb4ea3ec4f8e0e81fbf0756df88303152e10fa7dc38b5a
Timestamp: 1733672918 Timestamp [UCT]: 2024-12-08 15:48:38 Age [y:d:h:m:s]: 00:137:02:40:34
Block: 1170822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97785 RingCT/type: yes/0
Extra: 01e2451efca5e30cac14cb4ea3ec4f8e0e81fbf0756df88303152e10fa7dc38b5a021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 321960a8c01045fe3160a46c53916d20231700d425df4c4ef2858fba5703dc5d 0.600000000000 1656555 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": 1170832, "vin": [ { "gen": { "height": 1170822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "321960a8c01045fe3160a46c53916d20231700d425df4c4ef2858fba5703dc5d" } } ], "extra": [ 1, 226, 69, 30, 252, 165, 227, 12, 172, 20, 203, 78, 163, 236, 79, 142, 14, 129, 251, 240, 117, 109, 248, 131, 3, 21, 46, 16, 250, 125, 195, 139, 90, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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