Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af8db54158d3693d01807f373745c983df84edf5d83ceddfb1d9eade71636121

Tx prefix hash: b6aad40d9fe3dd94b3d615d2db513cea5aed8cfe50e7cddf6be7dfb8324e5ed2
Tx public key: acc77b0ea10a797c790529b9dfc8e53a3df7149c758050dcbc39da2c2952523c
Timestamp: 1751922013 Timestamp [UCT]: 2025-07-07 21:00:13 Age [y:d:h:m:s]: 00:135:21:58:07
Block: 1320848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95582 RingCT/type: yes/0
Extra: 01acc77b0ea10a797c790529b9dfc8e53a3df7149c758050dcbc39da2c2952523c02110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e73f1af7b3bf02698ab2526d93acd0e3cdecf5e70e508ec8347237303c715460 0.600000000000 1808549 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": 1320858, "vin": [ { "gen": { "height": 1320848 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e73f1af7b3bf02698ab2526d93acd0e3cdecf5e70e508ec8347237303c715460" } } ], "extra": [ 1, 172, 199, 123, 14, 161, 10, 121, 124, 121, 5, 41, 185, 223, 200, 229, 58, 61, 247, 20, 156, 117, 128, 80, 220, 188, 57, 218, 44, 41, 82, 82, 60, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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