Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8cfdc96063fefda5a100d03cc3a958434c341202cf7c22536eaa10bc645819c

Tx prefix hash: 3531d10a187d11f50f1a691bf6d3fb21846ba65469bce62ae5816789928780f3
Tx public key: 17376515a612b1e9623ed62c6d233583407f320ba7df87181b4df61c4c15a599
Timestamp: 1708394529 Timestamp [UCT]: 2024-02-20 02:02:09 Age [y:d:h:m:s]: 01:287:04:03:40
Block: 961337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 464023 RingCT/type: yes/0
Extra: 0117376515a612b1e9623ed62c6d233583407f320ba7df87181b4df61c4c15a59902110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a2bda2f77ffd8e0add2f4662e43e128a1b91884718908c76a3eac19368b75e3 0.600000000000 1420946 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": 961347, "vin": [ { "gen": { "height": 961337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a2bda2f77ffd8e0add2f4662e43e128a1b91884718908c76a3eac19368b75e3" } } ], "extra": [ 1, 23, 55, 101, 21, 166, 18, 177, 233, 98, 62, 214, 44, 109, 35, 53, 131, 64, 127, 50, 11, 167, 223, 135, 24, 27, 77, 246, 28, 76, 21, 165, 153, 2, 17, 0, 0, 0, 5, 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