Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e508557d70d31245a9426b9f85e74d14e03f7e9b05f8c1e6d61cd0961fc484b

Tx prefix hash: f1b7c53d298f9bb9edd0d1009918948c60383faf20ac5597b4806dc5c91e123f
Tx public key: 357bdf0aabf10f978b89c0e72a3bba87735c3591e370be767a720db6e1ed0a52
Timestamp: 1713539817 Timestamp [UCT]: 2024-04-19 15:16:57 Age [y:d:h:m:s]: 01:058:21:08:30
Block: 1003994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302960 RingCT/type: yes/0
Extra: 01357bdf0aabf10f978b89c0e72a3bba87735c3591e370be767a720db6e1ed0a520211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdf7a9a52b6d5a6ca1834e3599f7aa89f2225b3765068e2432244d5be4f9ff70 0.600000000000 1464550 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": 1004004, "vin": [ { "gen": { "height": 1003994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdf7a9a52b6d5a6ca1834e3599f7aa89f2225b3765068e2432244d5be4f9ff70" } } ], "extra": [ 1, 53, 123, 223, 10, 171, 241, 15, 151, 139, 137, 192, 231, 42, 59, 186, 135, 115, 92, 53, 145, 227, 112, 190, 118, 122, 114, 13, 182, 225, 237, 10, 82, 2, 17, 0, 0, 0, 8, 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