Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20a8f0f0e1b0d676efd1713cf8fff07162075f30319aa52b2744de99a2114ec0

Tx prefix hash: 9d1221827c32722aa7b0fe340eccc28f7c6e732a730218a03345851ed962b2b6
Tx public key: 17d7133d93784268b163d981593811e309b639a726cf29e36ec7a7ad8f7e8e01
Timestamp: 1763423675 Timestamp [UCT]: 2025-11-17 23:54:35 Age [y:d:h:m:s]: 00:051:22:17:25
Block: 1414431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37186 RingCT/type: yes/0
Extra: 0117d7133d93784268b163d981593811e309b639a726cf29e36ec7a7ad8f7e8e0102110000000234af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c3736e0c4098c93a5825b7c1da7138d948d8dd878bda088a12161e3595e80d7 0.600000000000 1902920 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": 1414441, "vin": [ { "gen": { "height": 1414431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c3736e0c4098c93a5825b7c1da7138d948d8dd878bda088a12161e3595e80d7" } } ], "extra": [ 1, 23, 215, 19, 61, 147, 120, 66, 104, 177, 99, 217, 129, 89, 56, 17, 227, 9, 182, 57, 167, 38, 207, 41, 227, 110, 199, 167, 173, 143, 126, 142, 1, 2, 17, 0, 0, 0, 2, 52, 175, 49, 204, 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