Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e0e203a504b144b82c14eb5c090ed0e94e3ad4c5ba11353149d20c2d663fd49

Tx prefix hash: 342085b0b2ab8ea75ee4bb26ba097d90d50e390fadea0e7f4a60a933851605c3
Tx public key: b440438d615303b3b5e38d55329f2b37d283ed4d78dc9ad6879200a324a751e9
Timestamp: 1713885216 Timestamp [UCT]: 2024-04-23 15:13:36 Age [y:d:h:m:s]: 00:204:17:25:19
Block: 1006864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146547 RingCT/type: yes/0
Extra: 01b440438d615303b3b5e38d55329f2b37d283ed4d78dc9ad6879200a324a751e902110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8402675341797eb63f41bc8184cea7413b5df801e14dd85295f42e5014f9a331 0.600000000000 1468026 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": 1006874, "vin": [ { "gen": { "height": 1006864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8402675341797eb63f41bc8184cea7413b5df801e14dd85295f42e5014f9a331" } } ], "extra": [ 1, 180, 64, 67, 141, 97, 83, 3, 179, 181, 227, 141, 85, 50, 159, 43, 55, 210, 131, 237, 77, 120, 220, 154, 214, 135, 146, 0, 163, 36, 167, 81, 233, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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