Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c807c7d4e8b477aab7521287d426c2c131b4c71f60317d18a6fad70c42795424

Tx prefix hash: 83ce5f2ec68ade18e70f0872c65243078741cdd1149d95354eb6e94a56f06b71
Tx public key: c41d1de308d227d4dbd3d6431e668da2a4c62c1ed6e16b93454dfa5dd14240c7
Timestamp: 1719347271 Timestamp [UCT]: 2024-06-25 20:27:51 Age [y:d:h:m:s]: 00:264:16:05:38
Block: 1052134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189137 RingCT/type: yes/0
Extra: 01c41d1de308d227d4dbd3d6431e668da2a4c62c1ed6e16b93454dfa5dd14240c70211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62cc7d1d6dcd61e9b2ade04fb32fc812353c319ececdace9541ee280a06348e9 0.600000000000 1522455 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": 1052144, "vin": [ { "gen": { "height": 1052134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62cc7d1d6dcd61e9b2ade04fb32fc812353c319ececdace9541ee280a06348e9" } } ], "extra": [ 1, 196, 29, 29, 227, 8, 210, 39, 212, 219, 211, 214, 67, 30, 102, 141, 162, 164, 198, 44, 30, 214, 225, 107, 147, 69, 77, 250, 93, 209, 66, 64, 199, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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