Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6841cd67d45ecd1300cb1f5ba0a527682f286458f81543f56a45ebd4bcc0fa7

Tx prefix hash: a5d6cf8c085967445d0e5c62518aa5be84d26f64754185ebf35ec6de182cfb8e
Tx public key: 5f39ad3e96c1ac65d81fde74f97c3c6efe2e710b9ab5a72d82d38101e81a5621
Timestamp: 1703824365 Timestamp [UCT]: 2023-12-29 04:32:45 Age [y:d:h:m:s]: 01:319:05:18:51
Block: 923452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486980 RingCT/type: yes/0
Extra: 015f39ad3e96c1ac65d81fde74f97c3c6efe2e710b9ab5a72d82d38101e81a56210211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3a219eead4f2c65b1f421501f5db4537a1d0ffbe6aba2ce21029932c97e3818 0.600000000000 1381184 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": 923462, "vin": [ { "gen": { "height": 923452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3a219eead4f2c65b1f421501f5db4537a1d0ffbe6aba2ce21029932c97e3818" } } ], "extra": [ 1, 95, 57, 173, 62, 150, 193, 172, 101, 216, 31, 222, 116, 249, 124, 60, 110, 254, 46, 113, 11, 154, 181, 167, 45, 130, 211, 129, 1, 232, 26, 86, 33, 2, 17, 0, 0, 0, 1, 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