Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08160d7dcd25c24dd3b19e53ddba3fcc23f147ae3adedb7e24fb9589c5c1e414

Tx prefix hash: bdcec4ea154dcc85c2e77244db3693ef0406a333ee0ed111efa9b2b8c40b84c8
Tx public key: 1ab4aa5af7bf9cb1ce2db12f8cd53493e9dcfdc621026fb38b94b5e945f06bb5
Timestamp: 1698423052 Timestamp [UCT]: 2023-10-27 16:10:52 Age [y:d:h:m:s]: 01:227:12:31:08
Block: 878895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423627 RingCT/type: yes/0
Extra: 011ab4aa5af7bf9cb1ce2db12f8cd53493e9dcfdc621026fb38b94b5e945f06bb50211000000024b8f5122000000000000000000

1 output(s) for total of 0.751373774000 dcy

stealth address amount amount idx
00: 0bdc68fce31d6cb7a5835025c112dedd5b1877703c50f294478838b40a5e8af8 0.751373774000 1334387 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": 878905, "vin": [ { "gen": { "height": 878895 } } ], "vout": [ { "amount": 751373774, "target": { "key": "0bdc68fce31d6cb7a5835025c112dedd5b1877703c50f294478838b40a5e8af8" } } ], "extra": [ 1, 26, 180, 170, 90, 247, 191, 156, 177, 206, 45, 177, 47, 140, 213, 52, 147, 233, 220, 253, 198, 33, 2, 111, 179, 139, 148, 181, 233, 69, 240, 107, 181, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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