Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6776a1e041a98c6aad2d92f2f80c9a506845ea674d2e4ccb917fae6d9034f39

Tx prefix hash: 71edcb714e3b858f766b8a44331726d86e72a2d62ef388eae80c1c5e6e11bdfc
Tx public key: bbbf41e7388e7dfb800d4f9dd7058dd8e97fbaee124d572506c9ab34cb7e5a65
Timestamp: 1726087163 Timestamp [UCT]: 2024-09-11 20:39:23 Age [y:d:h:m:s]: 00:101:22:36:16
Block: 1108019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72934 RingCT/type: yes/0
Extra: 01bbbf41e7388e7dfb800d4f9dd7058dd8e97fbaee124d572506c9ab34cb7e5a65021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d121b3e9c797df69ae4dba520e0823e918fe020b92eaabcac8c82f38951cf207 0.600000000000 1585766 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": 1108029, "vin": [ { "gen": { "height": 1108019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d121b3e9c797df69ae4dba520e0823e918fe020b92eaabcac8c82f38951cf207" } } ], "extra": [ 1, 187, 191, 65, 231, 56, 142, 125, 251, 128, 13, 79, 157, 215, 5, 141, 216, 233, 127, 186, 238, 18, 77, 87, 37, 6, 201, 171, 52, 203, 126, 90, 101, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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