Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d30dfc79f471ffb77e826cb02896ddf7b79fb633d2612d8024c161c78026b7b

Tx prefix hash: eb6e45cc57aeaa26cfd3097a2c250338a8e9bb679c63b388eb976944e972fe83
Tx public key: b315a6d9e7d35bd58b981d6f1426b9995fc7c5b2233cb47ff20d8c802fb45b06
Timestamp: 1708983349 Timestamp [UCT]: 2024-02-26 21:35:49 Age [y:d:h:m:s]: 01:111:13:26:42
Block: 966234 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340678 RingCT/type: yes/0
Extra: 01b315a6d9e7d35bd58b981d6f1426b9995fc7c5b2233cb47ff20d8c802fb45b060211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d175ea176a4475ca17ea34a14b421a040ef63b110a159dcbeb0784817555ebda 0.600000000000 1425991 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": 966244, "vin": [ { "gen": { "height": 966234 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d175ea176a4475ca17ea34a14b421a040ef63b110a159dcbeb0784817555ebda" } } ], "extra": [ 1, 179, 21, 166, 217, 231, 211, 91, 213, 139, 152, 29, 111, 20, 38, 185, 153, 95, 199, 197, 178, 35, 60, 180, 127, 242, 13, 140, 128, 47, 180, 91, 6, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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