Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5e17e453e23178a78185248a894c541c79e5d227c59fab8abf2553849a832b8

Tx prefix hash: 65ac5ff658be573374a265db6f41a7b29975fc00ebe63636ab417b91a57fb896
Tx public key: 054989770d0e681325dc3c10455255d3c8dc2c8291c91f765d5a21d2eda82f4b
Timestamp: 1719746675 Timestamp [UCT]: 2024-06-30 11:24:35 Age [y:d:h:m:s]: 00:345:16:04:42
Block: 1055445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247053 RingCT/type: yes/0
Extra: 01054989770d0e681325dc3c10455255d3c8dc2c8291c91f765d5a21d2eda82f4b02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a518be0292d908d69d0d3c406e7e6d3e9687be7c5a519a33f098771944f49763 0.600000000000 1525846 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": 1055455, "vin": [ { "gen": { "height": 1055445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a518be0292d908d69d0d3c406e7e6d3e9687be7c5a519a33f098771944f49763" } } ], "extra": [ 1, 5, 73, 137, 119, 13, 14, 104, 19, 37, 220, 60, 16, 69, 82, 85, 211, 200, 220, 44, 130, 145, 201, 31, 118, 93, 90, 33, 210, 237, 168, 47, 75, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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