Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a64a1d54107df9a8288f2765dd35b463d969040027b38549572ac25ba9d2a9d

Tx prefix hash: 7d5cf22e4522e396c81f5f744cf638ef69c8ebc3676c88fd9b238ae7cf62e353
Tx public key: 8e6b027d6c472c42ac57155fbacc63a755450493876949e57c010ae9e29dc0ba
Timestamp: 1745610112 Timestamp [UCT]: 2025-04-25 19:41:52 Age [y:d:h:m:s]: 00:214:20:45:14
Block: 1269366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151295 RingCT/type: yes/0
Extra: 018e6b027d6c472c42ac57155fbacc63a755450493876949e57c010ae9e29dc0ba0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f15bde0e60cf4c0f541b261a6091a753fce90810a18c3b9ac1ed2fc287b3bed4 0.600000000000 1756601 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": 1269376, "vin": [ { "gen": { "height": 1269366 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f15bde0e60cf4c0f541b261a6091a753fce90810a18c3b9ac1ed2fc287b3bed4" } } ], "extra": [ 1, 142, 107, 2, 125, 108, 71, 44, 66, 172, 87, 21, 95, 186, 204, 99, 167, 85, 69, 4, 147, 135, 105, 73, 229, 124, 1, 10, 233, 226, 157, 192, 186, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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