Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00d5550844d6942f3b7b02a9ed0d9f6ad7a0263ebc38c8d0907a004092da738f

Tx prefix hash: fd453786b937edb39cccc5a0347e97292df99794dd2e746dae0732ea356f8dec
Tx public key: 6b89973fe700b04d3f39be4e79e4491f4628765d0c198f1c96c684f0310e92c8
Timestamp: 1716797342 Timestamp [UCT]: 2024-05-27 08:09:02 Age [y:d:h:m:s]: 00:327:16:53:40
Block: 1031019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234216 RingCT/type: yes/0
Extra: 016b89973fe700b04d3f39be4e79e4491f4628765d0c198f1c96c684f0310e92c80211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10ebb50e487eb0ea619a77c064ce585dfbd2b08a026e128ce41a139b2c65c1b2 0.600000000000 1499360 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": 1031029, "vin": [ { "gen": { "height": 1031019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10ebb50e487eb0ea619a77c064ce585dfbd2b08a026e128ce41a139b2c65c1b2" } } ], "extra": [ 1, 107, 137, 151, 63, 231, 0, 176, 77, 63, 57, 190, 78, 121, 228, 73, 31, 70, 40, 118, 93, 12, 25, 143, 28, 150, 198, 132, 240, 49, 14, 146, 200, 2, 17, 0, 0, 0, 6, 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