Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b7b9e7275d6b0c96f315b1d0c3b3384cea24d09734452bf3cfccb1c9c30b7ed

Tx prefix hash: 02233e3c9b359edadba65e4a8878e5a66503ded8015ae329df940adb304021cb
Tx public key: 981a30fb08d6483c8dbee2d6ce8919410e9e167074bd543991e6e217b83233b5
Timestamp: 1707598140 Timestamp [UCT]: 2024-02-10 20:49:00 Age [y:d:h:m:s]: 00:291:14:18:08
Block: 954729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208775 RingCT/type: yes/0
Extra: 01981a30fb08d6483c8dbee2d6ce8919410e9e167074bd543991e6e217b83233b50211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c9582e555217d68483b6a7f190a3ae342f4cf942cd6b39ded54038bc4cc6015 0.600000000000 1414011 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": 954739, "vin": [ { "gen": { "height": 954729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c9582e555217d68483b6a7f190a3ae342f4cf942cd6b39ded54038bc4cc6015" } } ], "extra": [ 1, 152, 26, 48, 251, 8, 214, 72, 60, 141, 190, 226, 214, 206, 137, 25, 65, 14, 158, 22, 112, 116, 189, 84, 57, 145, 230, 226, 23, 184, 50, 51, 181, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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