Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3c4e2e186e1fcfaaeb3686853c6fb3d87811e08ef32b05067068d8c4a10870c

Tx prefix hash: 8b302701f5516da3678dd27beb066e76a1584d38080412f08726577f372d73ab
Tx public key: d0e24a4bf18c1c58b4bb0239f7c2a57eaf5382230b069b4326b4bb2abc00ac0a
Timestamp: 1761241042 Timestamp [UCT]: 2025-10-23 17:37:22 Age [y:d:h:m:s]: 00:071:20:07:01
Block: 1396357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51430 RingCT/type: yes/0
Extra: 01d0e24a4bf18c1c58b4bb0239f7c2a57eaf5382230b069b4326b4bb2abc00ac0a021100000005e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93fa54073f0dc983afbf877a240a25c65a88ca114cd0c5eca8e18040e20a0f4e 0.600000000000 1884642 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": 1396367, "vin": [ { "gen": { "height": 1396357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93fa54073f0dc983afbf877a240a25c65a88ca114cd0c5eca8e18040e20a0f4e" } } ], "extra": [ 1, 208, 226, 74, 75, 241, 140, 28, 88, 180, 187, 2, 57, 247, 194, 165, 126, 175, 83, 130, 35, 11, 6, 155, 67, 38, 180, 187, 42, 188, 0, 172, 10, 2, 17, 0, 0, 0, 5, 228, 220, 144, 9, 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