Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a5706b3f0a7d096e029693993d94fe77b785b9d6f82cdfa4aba092cf9a5e36f

Tx prefix hash: f2748533d67fd512286ec37150c0c8a3a0096edc217d1c651432e9b2d44389fe
Tx public key: a9d4832a87e016e7c717fdc2ac6afb94f756ee38e4b6716812ad891f0e189f3c
Timestamp: 1697231073 Timestamp [UCT]: 2023-10-13 21:04:33 Age [y:d:h:m:s]: 01:248:09:55:41
Block: 868990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438505 RingCT/type: yes/0
Extra: 01a9d4832a87e016e7c717fdc2ac6afb94f756ee38e4b6716812ad891f0e189f3c02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.810355201000 dcy

stealth address amount amount idx
00: 10c48acb5b8e822df788693a0c215b84bbe6943c90d9152842644d6d8a3b8d2a 0.810355201000 1323817 of 0

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": 869000, "vin": [ { "gen": { "height": 868990 } } ], "vout": [ { "amount": 810355201, "target": { "key": "10c48acb5b8e822df788693a0c215b84bbe6943c90d9152842644d6d8a3b8d2a" } } ], "extra": [ 1, 169, 212, 131, 42, 135, 224, 22, 231, 199, 23, 253, 194, 172, 106, 251, 148, 247, 86, 238, 56, 228, 182, 113, 104, 18, 173, 137, 31, 14, 24, 159, 60, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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