Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 084e7463bb3e57aa7c72cab0dfcaaba96b10f9774a2859e3d105c240465c415c

Tx prefix hash: 84fe02e8e22ce9b5e6f59f4aaaa92130d1b70ff762282ae5d0d5889e235469c1
Tx public key: 970b56f4ea8d783457577948ba28200ac07d3632dfe9dfb24797a26e810122e6
Timestamp: 1697200831 Timestamp [UCT]: 2023-10-13 12:40:31 Age [y:d:h:m:s]: 01:179:10:30:37
Block: 868739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389276 RingCT/type: yes/0
Extra: 01970b56f4ea8d783457577948ba28200ac07d3632dfe9dfb24797a26e810122e6021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.811908506000 dcy

stealth address amount amount idx
00: eac441484ed7bb3c36016fbc7791727f8cce8681fdf61f081b4676fe10d57f42 0.811908506000 1323558 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": 868749, "vin": [ { "gen": { "height": 868739 } } ], "vout": [ { "amount": 811908506, "target": { "key": "eac441484ed7bb3c36016fbc7791727f8cce8681fdf61f081b4676fe10d57f42" } } ], "extra": [ 1, 151, 11, 86, 244, 234, 141, 120, 52, 87, 87, 121, 72, 186, 40, 32, 10, 192, 125, 54, 50, 223, 233, 223, 178, 71, 151, 162, 110, 129, 1, 34, 230, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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