Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5f3617c49c78addb02049319ea01cf96aedefebd409dc7915f9b9622b6704eb

Tx prefix hash: 09fa18a1ef7e3c890e0c93d8fd29e4f93e1092420a814a9f5e512f3acd5ee82f
Tx public key: b826e84af6fb9d9b35b888ce9d774bfe03b3a52fd335e274c4dc3d3d3093aa20
Timestamp: 1729293516 Timestamp [UCT]: 2024-10-18 23:18:36 Age [y:d:h:m:s]: 00:222:14:46:24
Block: 1134599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158934 RingCT/type: yes/0
Extra: 01b826e84af6fb9d9b35b888ce9d774bfe03b3a52fd335e274c4dc3d3d3093aa200211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6619a0e2c02c04bee58a2ca398f8405986748da26b5ecf7da8a49a6c84ad1f06 0.600000000000 1617924 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": 1134609, "vin": [ { "gen": { "height": 1134599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6619a0e2c02c04bee58a2ca398f8405986748da26b5ecf7da8a49a6c84ad1f06" } } ], "extra": [ 1, 184, 38, 232, 74, 246, 251, 157, 155, 53, 184, 136, 206, 157, 119, 75, 254, 3, 179, 165, 47, 211, 53, 226, 116, 196, 220, 61, 61, 48, 147, 170, 32, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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