Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6ed29a070dde45cba22b34c5c3f062de638fdc54b1c62ee6b8cebde5f7d31b2

Tx prefix hash: c83c1be6eca81da6f8cd07df4fb4a2e2df37f4594fdcaca012fe5bd60a538616
Tx public key: 1a4fe7838a68ad50e8e1d6e8bfa424f075c62faa09caa71352fd74eed3c1b33d
Timestamp: 1731792745 Timestamp [UCT]: 2024-11-16 21:32:25 Age [y:d:h:m:s]: 00:125:23:53:11
Block: 1155217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89889 RingCT/type: yes/0
Extra: 011a4fe7838a68ad50e8e1d6e8bfa424f075c62faa09caa71352fd74eed3c1b33d0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1323a1ad4cfeb520ae655f8fd574a4fe4831f24971bee9bd962fa57064054ca 0.600000000000 1640832 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": 1155227, "vin": [ { "gen": { "height": 1155217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1323a1ad4cfeb520ae655f8fd574a4fe4831f24971bee9bd962fa57064054ca" } } ], "extra": [ 1, 26, 79, 231, 131, 138, 104, 173, 80, 232, 225, 214, 232, 191, 164, 36, 240, 117, 198, 47, 170, 9, 202, 167, 19, 82, 253, 116, 238, 211, 193, 179, 61, 2, 17, 0, 0, 0, 3, 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