Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eeb3747eb7fc1d8e8bb9bafaf007f5b1b03bd19f90c62b416a08ba37f26433c4

Tx prefix hash: 0668fdbdd50843d3a9e8f36b077c4326425dc1be8a8a7c183f3c7fdc65d3b72a
Tx public key: f912c1c617e016cadbaf3c1a9a20cde9d0a31669bcb4922ecc4a476a2cd95ea7
Timestamp: 1764461544 Timestamp [UCT]: 2025-11-30 00:12:24 Age [y:d:h:m:s]: 00:062:05:23:01
Block: 1423040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44358 RingCT/type: yes/0
Extra: 01f912c1c617e016cadbaf3c1a9a20cde9d0a31669bcb4922ecc4a476a2cd95ea702110000000117b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c03e52710dc96c1dc5671129e6bbc426f8337002c0d971f63e8eb21a1467f0e0 0.600000000000 1911641 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": 1423050, "vin": [ { "gen": { "height": 1423040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c03e52710dc96c1dc5671129e6bbc426f8337002c0d971f63e8eb21a1467f0e0" } } ], "extra": [ 1, 249, 18, 193, 198, 23, 224, 22, 202, 219, 175, 60, 26, 154, 32, 205, 233, 208, 163, 22, 105, 188, 180, 146, 46, 204, 74, 71, 106, 44, 217, 94, 167, 2, 17, 0, 0, 0, 1, 23, 177, 145, 50, 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