Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 854b7ba53bc18d6fcf1a2b52202c7e2509d7b4a8301a8b231797cbe662f32b89

Tx prefix hash: 7a777c5578d77044d92bac92592f4d667f2abfa944b66aa68365e06098aa5f72
Tx public key: dc77ec07a2594aa0986ebdd5c22f296914259912d0a5477d74f905dd4cc17c2d
Timestamp: 1763996231 Timestamp [UCT]: 2025-11-24 14:57:11 Age [y:d:h:m:s]: 00:027:17:35:55
Block: 1419181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19848 RingCT/type: yes/0
Extra: 01dc77ec07a2594aa0986ebdd5c22f296914259912d0a5477d74f905dd4cc17c2d021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a9f7bf75d7431c0f05d87722d497d5ff63380f84774e1adf12515fe0f2dae1f 0.600000000000 1907716 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": 1419191, "vin": [ { "gen": { "height": 1419181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a9f7bf75d7431c0f05d87722d497d5ff63380f84774e1adf12515fe0f2dae1f" } } ], "extra": [ 1, 220, 119, 236, 7, 162, 89, 74, 160, 152, 110, 189, 213, 194, 47, 41, 105, 20, 37, 153, 18, 208, 165, 71, 125, 116, 249, 5, 221, 76, 193, 124, 45, 2, 17, 0, 0, 0, 4, 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