Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1607d6aea2da819959b73e43fdc9a075b1ff4adb6e549f27cd960c0cdf65d2f5

Tx prefix hash: bc83444b021c434b13f84941f34ac0d922f17f21d080756521dfa57fe428b787
Tx public key: c81c02f7536ab8729528b90d9e97a8f390fc0ee0bc557fd29d25282f5784028e
Timestamp: 1760130688 Timestamp [UCT]: 2025-10-10 21:11:28 Age [y:d:h:m:s]: 00:042:03:10:32
Block: 1387144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30163 RingCT/type: yes/0
Extra: 01c81c02f7536ab8729528b90d9e97a8f390fc0ee0bc557fd29d25282f5784028e02110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6fc3930a923c3319f2c8ecc6e1be1e180b9e497b2efed869688c2b93b7fd91c 0.600000000000 1875331 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": 1387154, "vin": [ { "gen": { "height": 1387144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6fc3930a923c3319f2c8ecc6e1be1e180b9e497b2efed869688c2b93b7fd91c" } } ], "extra": [ 1, 200, 28, 2, 247, 83, 106, 184, 114, 149, 40, 185, 13, 158, 151, 168, 243, 144, 252, 14, 224, 188, 85, 127, 210, 157, 37, 40, 47, 87, 132, 2, 142, 2, 17, 0, 0, 0, 3, 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