Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b11cea4437b1c1c3c32f21caa1147aabcbd6d5e78c48fdf35c132dcd48e21909

Tx prefix hash: 98935ede517ef55bee7e94405f3c6e21f5b44855e6d353c0cd8ef45d09807043
Tx public key: b16d95ea596235d1de14d12a7d47eebf35649019424d4e6b9983c9d9ca2dbbfa
Timestamp: 1710585292 Timestamp [UCT]: 2024-03-16 10:34:52 Age [y:d:h:m:s]: 01:004:16:49:23
Block: 979523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264338 RingCT/type: yes/0
Extra: 01b16d95ea596235d1de14d12a7d47eebf35649019424d4e6b9983c9d9ca2dbbfa0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e344982adad69916479d9b84dce83857cb334d5551315d39547e040a9050c29c 0.600000000000 1439558 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": 979533, "vin": [ { "gen": { "height": 979523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e344982adad69916479d9b84dce83857cb334d5551315d39547e040a9050c29c" } } ], "extra": [ 1, 177, 109, 149, 234, 89, 98, 53, 209, 222, 20, 209, 42, 125, 71, 238, 191, 53, 100, 144, 25, 66, 77, 78, 107, 153, 131, 201, 217, 202, 45, 187, 250, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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