Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f361ceefc2a7de9f32d926c445112ae2a533a979408b9d5bd36e79da28a07add

Tx prefix hash: a8df839ee3413947f444babf4963fb28c12ae2afc4da3d48d650b3b4d5cd3dec
Tx public key: 511159b24037fdc090a46007f9c4b8794a29ffacd72150f5040da178f85b6f63
Timestamp: 1695957698 Timestamp [UCT]: 2023-09-29 03:21:38 Age [y:d:h:m:s]: 01:227:23:02:12
Block: 858438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424000 RingCT/type: yes/0
Extra: 01511159b24037fdc090a46007f9c4b8794a29ffacd72150f5040da178f85b6f630211000000104b8f5122000000000000000000

1 output(s) for total of 0.878291330000 dcy

stealth address amount amount idx
00: b43efd02da31eff8ce3f5e96d14be4e8dba8a9208cb6239be66306a3e47d08f9 0.878291330000 1312612 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": 858448, "vin": [ { "gen": { "height": 858438 } } ], "vout": [ { "amount": 878291330, "target": { "key": "b43efd02da31eff8ce3f5e96d14be4e8dba8a9208cb6239be66306a3e47d08f9" } } ], "extra": [ 1, 81, 17, 89, 178, 64, 55, 253, 192, 144, 164, 96, 7, 249, 196, 184, 121, 74, 41, 255, 172, 215, 33, 80, 245, 4, 13, 161, 120, 248, 91, 111, 99, 2, 17, 0, 0, 0, 16, 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