Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e12f0cc2f457906cbc5b64cf048b0cb7a35d3414f6d96cc26bb601d85a8d25d8

Tx prefix hash: b8d4c4148bef9ddf32752d3fba389630bceaa3a51e09d7bca8f5b7a595663f6a
Tx public key: 6c70bcd52c74e216c6a76a64ee8d0a428d4559efe5f9af7a2f7d9d575a572660
Timestamp: 1765902396 Timestamp [UCT]: 2025-12-16 16:26:36 Age [y:d:h:m:s]: 00:010:00:52:41
Block: 1434967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7188 RingCT/type: yes/0
Extra: 016c70bcd52c74e216c6a76a64ee8d0a428d4559efe5f9af7a2f7d9d575a5726600211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08e8c8d9c6f6a8404081932d220387a03471afb61587187ff383fd993560ee4e 0.600000000000 1923764 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": 1434977, "vin": [ { "gen": { "height": 1434967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08e8c8d9c6f6a8404081932d220387a03471afb61587187ff383fd993560ee4e" } } ], "extra": [ 1, 108, 112, 188, 213, 44, 116, 226, 22, 198, 167, 106, 100, 238, 141, 10, 66, 141, 69, 89, 239, 229, 249, 175, 122, 47, 125, 157, 87, 90, 87, 38, 96, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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