Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e6c9bceceac7b82ad6fc8a6e88a23c62147476d7cb10fdbc891f7f5d5656066

Tx prefix hash: 89c110e21dc12a8e145eb38ca08e731ab90f932c5acd9a9fa33c9839e0aa0db6
Tx public key: 375d58bd25141c01c28de5d310dc9f808617b865defd500a201388684eded04e
Timestamp: 1702301655 Timestamp [UCT]: 2023-12-11 13:34:15 Age [y:d:h:m:s]: 01:156:07:44:14
Block: 910824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372901 RingCT/type: yes/0
Extra: 01375d58bd25141c01c28de5d310dc9f808617b865defd500a201388684eded04e021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d18c3d82e149d821bb7ff056a6bdf3a1a7c6b003f2d7f6c1bafcecb155642a41 0.600000000000 1367997 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": 910834, "vin": [ { "gen": { "height": 910824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d18c3d82e149d821bb7ff056a6bdf3a1a7c6b003f2d7f6c1bafcecb155642a41" } } ], "extra": [ 1, 55, 93, 88, 189, 37, 20, 28, 1, 194, 141, 229, 211, 16, 220, 159, 128, 134, 23, 184, 101, 222, 253, 80, 10, 32, 19, 136, 104, 78, 222, 208, 78, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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