Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd9c853db45d59cb65a94d8a34dcb838c2ae0ac372a44613c72074399d481990

Tx prefix hash: 6a2d5b108bbbb58e3d5ee0ceba828a725d8ce5546dc910c14bc406f6b5a4e4a3
Tx public key: 1d28a182e80fe5b2ccc497d9eba30bc66ab707de9d0afbbdce69fff7138dd8e0
Timestamp: 1739193513 Timestamp [UCT]: 2025-02-10 13:18:33 Age [y:d:h:m:s]: 00:328:12:16:47
Block: 1216244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232614 RingCT/type: yes/0
Extra: 011d28a182e80fe5b2ccc497d9eba30bc66ab707de9d0afbbdce69fff7138dd8e00211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8da4bc1947ecddb20d77ff5eb9367a5bd5580170de95fce4f67a07a771d24bfe 0.600000000000 1703049 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": 1216254, "vin": [ { "gen": { "height": 1216244 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8da4bc1947ecddb20d77ff5eb9367a5bd5580170de95fce4f67a07a771d24bfe" } } ], "extra": [ 1, 29, 40, 161, 130, 232, 15, 229, 178, 204, 196, 151, 217, 235, 163, 11, 198, 106, 183, 7, 222, 157, 10, 251, 189, 206, 105, 255, 247, 19, 141, 216, 224, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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