Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec282d8cc0fa1b1fa0f1a778da25388f3f3750640f756a7af430f1586223a2d9

Tx prefix hash: 045d31c3f6d90e2bf564d31622088b95a62ddc773967153e95422dbb16c257dc
Tx public key: a889dc79f0b2f0b19efd999af0c6f4f648a0629826f52830c3385fcb90faad31
Timestamp: 1703934323 Timestamp [UCT]: 2023-12-30 11:05:23 Age [y:d:h:m:s]: 01:312:18:50:12
Block: 924357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482380 RingCT/type: yes/0
Extra: 01a889dc79f0b2f0b19efd999af0c6f4f648a0629826f52830c3385fcb90faad310211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad3c6ff79a6eabdfcbdd52555a62ad49e17ff4c31ce0358995b8009b31d15c81 0.600000000000 1382103 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": 924367, "vin": [ { "gen": { "height": 924357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad3c6ff79a6eabdfcbdd52555a62ad49e17ff4c31ce0358995b8009b31d15c81" } } ], "extra": [ 1, 168, 137, 220, 121, 240, 178, 240, 177, 158, 253, 153, 154, 240, 198, 244, 246, 72, 160, 98, 152, 38, 245, 40, 48, 195, 56, 95, 203, 144, 250, 173, 49, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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