Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53e630d0cc2fb6e063f89a9eb8412f5d7eb73f4e782f19eed288e353716145d5

Tx prefix hash: 3f6e73f972f617a7a055d6d017ddbbfdebffee2d0bd6b95379f33aa9ac3a5efe
Tx public key: 40ddbc467f43ff3c10143f9ce9e5a3622784cc3a44287cda7b432dc8fb0eface
Timestamp: 1714367174 Timestamp [UCT]: 2024-04-29 05:06:14 Age [y:d:h:m:s]: 00:305:05:04:11
Block: 1010854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218148 RingCT/type: yes/0
Extra: 0140ddbc467f43ff3c10143f9ce9e5a3622784cc3a44287cda7b432dc8fb0eface0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c25f54291e12c8b4301a96277d86808d64121f923587ef7275ed385de928363 0.600000000000 1472920 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": 1010864, "vin": [ { "gen": { "height": 1010854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c25f54291e12c8b4301a96277d86808d64121f923587ef7275ed385de928363" } } ], "extra": [ 1, 64, 221, 188, 70, 127, 67, 255, 60, 16, 20, 63, 156, 233, 229, 163, 98, 39, 132, 204, 58, 68, 40, 124, 218, 123, 67, 45, 200, 251, 14, 250, 206, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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