Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 600d593fcf678dfa6aaa53c35912c308f5d1efd9b9135b0c1b64e802a6674074

Tx prefix hash: e871bd508aa1b2706e9a0d421af4d7413a02672fc91919458c80b26081c89a96
Tx public key: 5beaf3f0963df23d61c58523b16b98a9378523af94966b73dfdcc39171ac221e
Timestamp: 1702576970 Timestamp [UCT]: 2023-12-14 18:02:50 Age [y:d:h:m:s]: 01:331:09:38:33
Block: 913108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495704 RingCT/type: yes/0
Extra: 015beaf3f0963df23d61c58523b16b98a9378523af94966b73dfdcc39171ac221e02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5806c02cd7b3f5d2b8316695c3dfbec7e4630b23cf8a6877d7fa1dd629c3316b 0.600000000000 1370354 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": 913118, "vin": [ { "gen": { "height": 913108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5806c02cd7b3f5d2b8316695c3dfbec7e4630b23cf8a6877d7fa1dd629c3316b" } } ], "extra": [ 1, 91, 234, 243, 240, 150, 61, 242, 61, 97, 197, 133, 35, 177, 107, 152, 169, 55, 133, 35, 175, 148, 150, 107, 115, 223, 220, 195, 145, 113, 172, 34, 30, 2, 17, 0, 0, 0, 4, 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