Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d720184bd3d470c632e84a7e4036c99f425083a630cf49f3c1215177cb98493

Tx prefix hash: 994fd0d13d2f67fbc7b227db71edd098291a70ee8ee749faa67fdcb4abffaf6c
Tx public key: d42960adb9ad3f5f5dcfb92a5d663641d67fa1af610ef6a0b017a304105f840a
Timestamp: 1764678817 Timestamp [UCT]: 2025-12-02 12:33:37 Age [y:d:h:m:s]: 00:062:01:17:29
Block: 1424841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44249 RingCT/type: yes/0
Extra: 01d42960adb9ad3f5f5dcfb92a5d663641d67fa1af610ef6a0b017a304105f840a021100000004da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62c605e38df7c0ca3a5aa78ca1287227580e09a54272633a84a8a71804fad6bb 0.600000000000 1913472 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": 1424851, "vin": [ { "gen": { "height": 1424841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62c605e38df7c0ca3a5aa78ca1287227580e09a54272633a84a8a71804fad6bb" } } ], "extra": [ 1, 212, 41, 96, 173, 185, 173, 63, 95, 93, 207, 185, 42, 93, 102, 54, 65, 214, 127, 161, 175, 97, 14, 246, 160, 176, 23, 163, 4, 16, 95, 132, 10, 2, 17, 0, 0, 0, 4, 218, 85, 72, 72, 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