Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0164f6f7bc96a7f96b4f78f4dfe2045ecb207578f42e2d1cd4ec393ceb771ff9

Tx prefix hash: 5b58764824dc5c71683464c13e04e1976e8d00d1ae2d7e1ef8d4577151c35e91
Tx public key: eceaa1c7051722f7a495c7621403cff9b7342b81c30d3347f9191b30e9fe9b2e
Timestamp: 1738445254 Timestamp [UCT]: 2025-02-01 21:27:34 Age [y:d:h:m:s]: 00:292:10:18:05
Block: 1210040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206760 RingCT/type: yes/0
Extra: 01eceaa1c7051722f7a495c7621403cff9b7342b81c30d3347f9191b30e9fe9b2e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e95aab17845de81a3287aa5b64778e2a6d500bfec3e7bf07921e24fd5e276d15 0.600000000000 1696787 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": 1210050, "vin": [ { "gen": { "height": 1210040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e95aab17845de81a3287aa5b64778e2a6d500bfec3e7bf07921e24fd5e276d15" } } ], "extra": [ 1, 236, 234, 161, 199, 5, 23, 34, 247, 164, 149, 199, 98, 20, 3, 207, 249, 183, 52, 43, 129, 195, 13, 51, 71, 249, 25, 27, 48, 233, 254, 155, 46, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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