Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a63136c9b1281a0ddbdd612eb701cfe75aaec0a3d371e2ca0d350ac05a9b4f8b

Tx prefix hash: 8face57f77ce57b38400767995f5cbebe46295df65a9815599be8043ae805f95
Tx public key: 9f0ad55c4693c54cf58277470e3049f0ccc7f23c81abf1e2aa1076f111f072e0
Timestamp: 1699624558 Timestamp [UCT]: 2023-11-10 13:55:58 Age [y:d:h:m:s]: 01:186:19:42:11
Block: 888638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394728 RingCT/type: yes/0
Extra: 019f0ad55c4693c54cf58277470e3049f0ccc7f23c81abf1e2aa1076f111f072e0021100000009faf35c9c000000000000000000

1 output(s) for total of 0.697546903000 dcy

stealth address amount amount idx
00: 816253966fd27a3bb059d12d6ebb28b460de0bd6ec34840c5c692a507578a128 0.697546903000 1344591 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": 888648, "vin": [ { "gen": { "height": 888638 } } ], "vout": [ { "amount": 697546903, "target": { "key": "816253966fd27a3bb059d12d6ebb28b460de0bd6ec34840c5c692a507578a128" } } ], "extra": [ 1, 159, 10, 213, 92, 70, 147, 197, 76, 245, 130, 119, 71, 14, 48, 73, 240, 204, 199, 242, 60, 129, 171, 241, 226, 170, 16, 118, 241, 17, 240, 114, 224, 2, 17, 0, 0, 0, 9, 250, 243, 92, 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