Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a82b339a109c5590543fd8d497b198649b135c798a883f910d2c4867959471d

Tx prefix hash: 17cc8e8e83e9d0d65a32b7ff9ee4356d80cc4871a5adb1af1ec72184e3764e40
Tx public key: 422e3c908cae1ebc9757d40cc23cb54ddc07d0e51910245875f5db1f4624720e
Timestamp: 1757770034 Timestamp [UCT]: 2025-09-13 13:27:14 Age [y:d:h:m:s]: 00:057:08:36:52
Block: 1367578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41079 RingCT/type: yes/0
Extra: 01422e3c908cae1ebc9757d40cc23cb54ddc07d0e51910245875f5db1f4624720e021100000011b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e40caf9eb51911a70d20217f258c87d0c299f10065413c636f081a670b018225 0.600000000000 1855617 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": 1367588, "vin": [ { "gen": { "height": 1367578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e40caf9eb51911a70d20217f258c87d0c299f10065413c636f081a670b018225" } } ], "extra": [ 1, 66, 46, 60, 144, 140, 174, 30, 188, 151, 87, 212, 12, 194, 60, 181, 77, 220, 7, 208, 229, 25, 16, 36, 88, 117, 245, 219, 31, 70, 36, 114, 14, 2, 17, 0, 0, 0, 17, 178, 247, 132, 196, 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