Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37a515d21312bd5d612ea21da912d74ea106e09a7f0651533feafa7a9488564c

Tx prefix hash: e2a49abf6992b5a4b01e73fd937183152cc04181314195b9aca021d50641f265
Tx public key: 7c203d8b34a20df78edec5499d57db8f7405d33579c1f6061a4b79a6cdc6bfd3
Timestamp: 1719831125 Timestamp [UCT]: 2024-07-01 10:52:05 Age [y:d:h:m:s]: 01:130:04:52:22
Block: 1056148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351595 RingCT/type: yes/0
Extra: 017c203d8b34a20df78edec5499d57db8f7405d33579c1f6061a4b79a6cdc6bfd302110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8fdb31e2549b8223788633771d3fb2f8dd51d68bc73b050f8c2728ffb33953eb 0.600000000000 1526559 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": 1056158, "vin": [ { "gen": { "height": 1056148 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8fdb31e2549b8223788633771d3fb2f8dd51d68bc73b050f8c2728ffb33953eb" } } ], "extra": [ 1, 124, 32, 61, 139, 52, 162, 13, 247, 142, 222, 197, 73, 157, 87, 219, 143, 116, 5, 211, 53, 121, 193, 246, 6, 26, 75, 121, 166, 205, 198, 191, 211, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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