Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50fd2196e43a717f243ace645ad8e59211b85cdaf9a9102be14bd691951d5ffb

Tx prefix hash: 824045e7317245a8faf6891931dfd1e501755884a16f3d5edc7d3a97a13abeec
Tx public key: ebe557d13b133028665bec0a5f5b5ae05bb40f0c98f2c689920c8e5d6b6e0557
Timestamp: 1736756046 Timestamp [UCT]: 2025-01-13 08:14:06 Age [y:d:h:m:s]: 00:095:00:58:34
Block: 1196332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67711 RingCT/type: yes/0
Extra: 01ebe557d13b133028665bec0a5f5b5ae05bb40f0c98f2c689920c8e5d6b6e0557021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5301b1c52f7220fa353fbdae84100181e479f3710fcc2ee7a2099e2ad3b48292 0.600000000000 1682931 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": 1196342, "vin": [ { "gen": { "height": 1196332 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5301b1c52f7220fa353fbdae84100181e479f3710fcc2ee7a2099e2ad3b48292" } } ], "extra": [ 1, 235, 229, 87, 209, 59, 19, 48, 40, 102, 91, 236, 10, 95, 91, 90, 224, 91, 180, 15, 12, 152, 242, 198, 137, 146, 12, 142, 93, 107, 110, 5, 87, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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