Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac895c620313e092ab9058936526b429d0ed596efa5097452fa7f95a74ec9fe4

Tx prefix hash: b9b493e8d8b7ee86118ed2ea618c1269177611c0f5331b37b6ee359e619875d6
Tx public key: b847ff0679b14d8b6ed1e0d6d3416cf851a3d79e50d47a5ca20349d65f3b8bfd
Timestamp: 1764161240 Timestamp [UCT]: 2025-11-26 12:47:20 Age [y:d:h:m:s]: 00:000:20:27:46
Block: 1420540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 622 RingCT/type: yes/0
Extra: 01b847ff0679b14d8b6ed1e0d6d3416cf851a3d79e50d47a5ca20349d65f3b8bfd0211000000044e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e30eac99fcffe3f398505813150fa7aa486e8f94d6159c251c272fcac9c48754 0.600000000000 1909085 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": 1420550, "vin": [ { "gen": { "height": 1420540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e30eac99fcffe3f398505813150fa7aa486e8f94d6159c251c272fcac9c48754" } } ], "extra": [ 1, 184, 71, 255, 6, 121, 177, 77, 139, 110, 209, 224, 214, 211, 65, 108, 248, 81, 163, 215, 158, 80, 212, 122, 92, 162, 3, 73, 214, 95, 59, 139, 253, 2, 17, 0, 0, 0, 4, 78, 123, 252, 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