Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0f83bab13471404e2124fa921efb5d00e5001a62cd5adc7827a5e7d201466ea

Tx prefix hash: e9a7eee0ef4d43284982394d71cd92f05281e764778c5c9e018457c7928c6cc4
Tx public key: 1ced93b1f318d8e7fd3cbcfe316e778c6a1f1c2cb8aebd72b4089c4aae4ceda2
Timestamp: 1755944496 Timestamp [UCT]: 2025-08-23 10:21:36 Age [y:d:h:m:s]: 00:089:21:22:58
Block: 1352629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64170 RingCT/type: yes/0
Extra: 011ced93b1f318d8e7fd3cbcfe316e778c6a1f1c2cb8aebd72b4089c4aae4ceda20211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1583992309aebffc6bff409e8e65df37d4239834562b6327d1f35a3d4204de7 0.600000000000 1840596 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": 1352639, "vin": [ { "gen": { "height": 1352629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1583992309aebffc6bff409e8e65df37d4239834562b6327d1f35a3d4204de7" } } ], "extra": [ 1, 28, 237, 147, 177, 243, 24, 216, 231, 253, 60, 188, 254, 49, 110, 119, 140, 106, 31, 28, 44, 184, 174, 189, 114, 180, 8, 156, 74, 174, 76, 237, 162, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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