Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99dfdfc18fe7412ec00ea6f438feb315e3aa6aa64d02990f7d2e79d974fd1bf6

Tx prefix hash: 5715d826b396af2f15f5b5c1f5169c139190395112000b7d3fbd205e66795208
Tx public key: 51a47a2a7a912d9137382ce2452d9973ad2f73c721aa051e65206dcefed78b52
Timestamp: 1765009045 Timestamp [UCT]: 2025-12-06 08:17:25 Age [y:d:h:m:s]: 00:051:07:01:31
Block: 1427563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36551 RingCT/type: yes/0
Extra: 0151a47a2a7a912d9137382ce2452d9973ad2f73c721aa051e65206dcefed78b52021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ed9921cbebad5c37c43957ea5fda60111407492b69c1ebc9a960c139b0de7c4 0.600000000000 1916266 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": 1427573, "vin": [ { "gen": { "height": 1427563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ed9921cbebad5c37c43957ea5fda60111407492b69c1ebc9a960c139b0de7c4" } } ], "extra": [ 1, 81, 164, 122, 42, 122, 145, 45, 145, 55, 56, 44, 226, 69, 45, 153, 115, 173, 47, 115, 199, 33, 170, 5, 30, 101, 32, 109, 206, 254, 215, 139, 82, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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