Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ea51aacac51867e9e0fba30fbbd8b2e7568d8f94601f544bc7843a084b48a79

Tx prefix hash: 44ffcf2a5d7ad186226c7f8fd0037b260043b4a794a9c0cea676b6138a516ca6
Tx public key: ccd98c62e13a9a45398581021dab19c3e946eb5bd5c7b9311db11b78d9da67b4
Timestamp: 1704225842 Timestamp [UCT]: 2024-01-02 20:04:02 Age [y:d:h:m:s]: 01:091:07:14:14
Block: 926771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326356 RingCT/type: yes/0
Extra: 01ccd98c62e13a9a45398581021dab19c3e946eb5bd5c7b9311db11b78d9da67b402110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f511cfc8a3cebd7ff012f25e225ac193496b103aee96315188fd5af2e007497 0.600000000000 1384569 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": 926781, "vin": [ { "gen": { "height": 926771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f511cfc8a3cebd7ff012f25e225ac193496b103aee96315188fd5af2e007497" } } ], "extra": [ 1, 204, 217, 140, 98, 225, 58, 154, 69, 57, 133, 129, 2, 29, 171, 25, 195, 233, 70, 235, 91, 213, 199, 185, 49, 29, 177, 27, 120, 217, 218, 103, 180, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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