Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 622331af525035f6c16a75cb9d57f79815ca17c89377b92524c19e5eb656ec1a

Tx prefix hash: 041eabf1dbc6492f2d0d69dff7318f42d391cfbe0260e08e13bbf8b11382e1c2
Tx public key: 9ca498d93111c2e28b97287cdf5cf44c3e7d8810b54e8593e4d459bf1116e180
Timestamp: 1697125561 Timestamp [UCT]: 2023-10-12 15:46:01 Age [y:d:h:m:s]: 01:178:21:35:55
Block: 868134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388866 RingCT/type: yes/0
Extra: 019ca498d93111c2e28b97287cdf5cf44c3e7d8810b54e8593e4d459bf1116e18002110000000b4b8f5122000000000000000000

1 output(s) for total of 0.815664777000 dcy

stealth address amount amount idx
00: cedde73bfc44653b6ce9717decd1bd71501e519833ecce820b93784ba9d47b7c 0.815664777000 1322905 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": 868144, "vin": [ { "gen": { "height": 868134 } } ], "vout": [ { "amount": 815664777, "target": { "key": "cedde73bfc44653b6ce9717decd1bd71501e519833ecce820b93784ba9d47b7c" } } ], "extra": [ 1, 156, 164, 152, 217, 49, 17, 194, 226, 139, 151, 40, 124, 223, 92, 244, 76, 62, 125, 136, 16, 181, 78, 133, 147, 228, 212, 89, 191, 17, 22, 225, 128, 2, 17, 0, 0, 0, 11, 75, 143, 81, 34, 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