Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2e5386d1f9bfac16e689d34d0e5c6fa62786ff97f60959411f68d9962ecb6f8

Tx prefix hash: d862123e11bb53537ecad9739577f55de8e2a96f9c5d15dc9b0b71bc6e3997c3
Tx public key: 12cc538223f533ab5f399cb52477fd68ba5ec7ee107233e7dd80df9c7128f0f7
Timestamp: 1710740452 Timestamp [UCT]: 2024-03-18 05:40:52 Age [y:d:h:m:s]: 01:080:01:16:09
Block: 980807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318227 RingCT/type: yes/0
Extra: 0112cc538223f533ab5f399cb52477fd68ba5ec7ee107233e7dd80df9c7128f0f702110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ae30446e1d8d7c2ed33014a19ad291522365069ef4d7945de945e1520c092f1 0.600000000000 1440888 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": 980817, "vin": [ { "gen": { "height": 980807 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ae30446e1d8d7c2ed33014a19ad291522365069ef4d7945de945e1520c092f1" } } ], "extra": [ 1, 18, 204, 83, 130, 35, 245, 51, 171, 95, 57, 156, 181, 36, 119, 253, 104, 186, 94, 199, 238, 16, 114, 51, 231, 221, 128, 223, 156, 113, 40, 240, 247, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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