Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f82549ce648740b7736e1246ccda1a86ed4e4bc22ca382698f89eb4480f23350

Tx prefix hash: ae05d043c85b54ab3011f4d6ab4fa45a7093fd7954c775a11af5d1a214a26e3f
Tx public key: 968d83f35fa25448eac20e6314a654a7598864b2bbc4667fb4dcb6d3a2359f5d
Timestamp: 1741125377 Timestamp [UCT]: 2025-03-04 21:56:17 Age [y:d:h:m:s]: 00:261:22:22:20
Block: 1232233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184954 RingCT/type: yes/0
Extra: 01968d83f35fa25448eac20e6314a654a7598864b2bbc4667fb4dcb6d3a2359f5d0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4b09865987af59d0545fbda757ae0fbadec2a887507fa1dad5d8a2ff0fe4c3b 0.600000000000 1719146 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": 1232243, "vin": [ { "gen": { "height": 1232233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4b09865987af59d0545fbda757ae0fbadec2a887507fa1dad5d8a2ff0fe4c3b" } } ], "extra": [ 1, 150, 141, 131, 243, 95, 162, 84, 72, 234, 194, 14, 99, 20, 166, 84, 167, 89, 136, 100, 178, 187, 196, 102, 127, 180, 220, 182, 211, 162, 53, 159, 93, 2, 17, 0, 0, 0, 6, 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