Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36e39c64c9dc44bd89d3c821a92539505d19d8265ba56bf4fb64da4148583e93

Tx prefix hash: e88d398d7c92f0e280da8e9ade32749cd2aea947e5ab9cdadcba0680143422ae
Tx public key: 6e529f60f6d36f4a1fe79cf63d65c757be047fa24d4c72c567f4a2dcd2ee3531
Timestamp: 1728319988 Timestamp [UCT]: 2024-10-07 16:53:08 Age [y:d:h:m:s]: 00:166:05:03:06
Block: 1126529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118584 RingCT/type: yes/0
Extra: 016e529f60f6d36f4a1fe79cf63d65c757be047fa24d4c72c567f4a2dcd2ee3531021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 871bd34ead14d27bdfb45fbca52041eb78ed8990f7169b58744552de7fdbf760 0.600000000000 1609324 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": 1126539, "vin": [ { "gen": { "height": 1126529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "871bd34ead14d27bdfb45fbca52041eb78ed8990f7169b58744552de7fdbf760" } } ], "extra": [ 1, 110, 82, 159, 96, 246, 211, 111, 74, 31, 231, 156, 246, 61, 101, 199, 87, 190, 4, 127, 162, 77, 76, 114, 197, 103, 244, 162, 220, 210, 238, 53, 49, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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