Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a09b821be131854b3b8bfffd5a4b2474132c782c160deff89d9967b49dcb753

Tx prefix hash: 1613faecb9053ad9b02bd554049a53c4584404153216fab1153124f055576136
Tx public key: bbaec99daa1706963afeae814c512ebf1088c2afa6db3dc0fbf781b594bb7e4c
Timestamp: 1702603127 Timestamp [UCT]: 2023-12-15 01:18:47 Age [y:d:h:m:s]: 01:037:07:05:45
Block: 913322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287969 RingCT/type: yes/0
Extra: 01bbaec99daa1706963afeae814c512ebf1088c2afa6db3dc0fbf781b594bb7e4c02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39b0d016ba86323fd2f8473e86ea34b525bbbedb5ce51a0e108e6fb7b3bf45f0 0.600000000000 1370588 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": 913332, "vin": [ { "gen": { "height": 913322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39b0d016ba86323fd2f8473e86ea34b525bbbedb5ce51a0e108e6fb7b3bf45f0" } } ], "extra": [ 1, 187, 174, 201, 157, 170, 23, 6, 150, 58, 254, 174, 129, 76, 81, 46, 191, 16, 136, 194, 175, 166, 219, 61, 192, 251, 247, 129, 181, 148, 187, 126, 76, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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