Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1931d2526d75f44501c46befa226b1b3bb7e8440e310d192d9cfba2c81e54eaa

Tx prefix hash: 26dd046a416b91275745bb527992e2136f4c14de9e50e7bc13f8a210c0610231
Tx public key: 7a63ba3946258897dc4c1ab51fd18c4ce08c37f0af763d2db5ef366d6181e517
Timestamp: 1766070940 Timestamp [UCT]: 2025-12-18 15:15:40 Age [y:d:h:m:s]: 00:003:09:01:26
Block: 1436367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2422 RingCT/type: yes/0
Extra: 017a63ba3946258897dc4c1ab51fd18c4ce08c37f0af763d2db5ef366d6181e51702110000000370609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d86b3e48e941486d66c9ae8b796e6ed9166b533a9d5c4d4898abe2e90fd4d51 0.600000000000 1925172 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": 1436377, "vin": [ { "gen": { "height": 1436367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d86b3e48e941486d66c9ae8b796e6ed9166b533a9d5c4d4898abe2e90fd4d51" } } ], "extra": [ 1, 122, 99, 186, 57, 70, 37, 136, 151, 220, 76, 26, 181, 31, 209, 140, 76, 224, 140, 55, 240, 175, 118, 61, 45, 181, 239, 54, 109, 97, 129, 229, 23, 2, 17, 0, 0, 0, 3, 112, 96, 157, 3, 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