Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ef9dc62e86e0839656cd3b32eeae7d755a16cda1cfe7d3fda590af730a9f081

Tx prefix hash: 78940b79041e92a3342920ecc21e296e0b3b15a642bc3504e7e74206d0395f27
Tx public key: e3da773ede39ad031cf4d04a5f8c474abde856409c51db2bd11e87a0c70b4576
Timestamp: 1736607871 Timestamp [UCT]: 2025-01-11 15:04:31 Age [y:d:h:m:s]: 00:158:22:06:13
Block: 1195100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113280 RingCT/type: yes/0
Extra: 01e3da773ede39ad031cf4d04a5f8c474abde856409c51db2bd11e87a0c70b45760211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0144c3d5d0efd268393ce3c1f9fb7eb0147767a72e41133eb1eddca3d22bb2f 0.600000000000 1681685 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": 1195110, "vin": [ { "gen": { "height": 1195100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0144c3d5d0efd268393ce3c1f9fb7eb0147767a72e41133eb1eddca3d22bb2f" } } ], "extra": [ 1, 227, 218, 119, 62, 222, 57, 173, 3, 28, 244, 208, 74, 95, 140, 71, 74, 189, 232, 86, 64, 156, 81, 219, 43, 209, 30, 135, 160, 199, 11, 69, 118, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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