Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85e4b38bf4347afde9aef850673cb74a5f123cb3ac583eeb971dc8ee3364032c

Tx prefix hash: ab10e38c2eeb72a94a87eb04e37216bb81f61f92910a96e40f5c630d3070dc68
Tx public key: 713fa4a914b49bc5eccbc3a68158dc1a84a67883080dd9ad69ddb5cbe00931c2
Timestamp: 1759871634 Timestamp [UCT]: 2025-10-07 21:13:54 Age [y:d:h:m:s]: 00:033:03:12:41
Block: 1384986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23734 RingCT/type: yes/0
Extra: 01713fa4a914b49bc5eccbc3a68158dc1a84a67883080dd9ad69ddb5cbe00931c2021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a6d16fd9619a7c9db950940523185c92fca7b14b6638f84cd430e4c98cbbed7 0.600000000000 1873143 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": 1384996, "vin": [ { "gen": { "height": 1384986 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a6d16fd9619a7c9db950940523185c92fca7b14b6638f84cd430e4c98cbbed7" } } ], "extra": [ 1, 113, 63, 164, 169, 20, 180, 155, 197, 236, 203, 195, 166, 129, 88, 220, 26, 132, 166, 120, 131, 8, 13, 217, 173, 105, 221, 181, 203, 224, 9, 49, 194, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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