Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f57bc2453b5ef353956af19f7a438ab8cd936697dbd5cd0f548c6a2477bdf9b8

Tx prefix hash: 92bea6741657307ab9317fada82a981afd9416d1fbdf31d4e31fc4846826e49c
Tx public key: 358c6cb73aef67d023ed4107dd9de5dae082a6e181cfa8393a6eec7fb19c96c6
Timestamp: 1708587338 Timestamp [UCT]: 2024-02-22 07:35:38 Age [y:d:h:m:s]: 01:030:16:39:31
Block: 962931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282952 RingCT/type: yes/0
Extra: 01358c6cb73aef67d023ed4107dd9de5dae082a6e181cfa8393a6eec7fb19c96c60211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b392b00bb14110a6d13a61817432b2ad1d194cdd513cc21c411f4f22d0448a45 0.600000000000 1422620 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": 962941, "vin": [ { "gen": { "height": 962931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b392b00bb14110a6d13a61817432b2ad1d194cdd513cc21c411f4f22d0448a45" } } ], "extra": [ 1, 53, 140, 108, 183, 58, 239, 103, 208, 35, 237, 65, 7, 221, 157, 229, 218, 224, 130, 166, 225, 129, 207, 168, 57, 58, 110, 236, 127, 177, 156, 150, 198, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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