Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a96e8ce835b01ebbbaa6c04de9b123a94c3cfe2bc619cff289ba1ba488e6c22

Tx prefix hash: 4ad263d1e4d3cfc230b10f2303a362d8bcac98adcf73631d8c41cbbe967008a3
Tx public key: 0dce6f9ee3373d4f45f11d8b2a2ab19acce7eea7ec7cbbff242a6dba0faa1898
Timestamp: 1717777478 Timestamp [UCT]: 2024-06-07 16:24:38 Age [y:d:h:m:s]: 00:179:13:20:11
Block: 1039137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128504 RingCT/type: yes/0
Extra: 010dce6f9ee3373d4f45f11d8b2a2ab19acce7eea7ec7cbbff242a6dba0faa189802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44f7ba506ae2b4b361b9af006f42a47e783fc7f3371584561edd8c4bb07f9bcc 0.600000000000 1507746 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": 1039147, "vin": [ { "gen": { "height": 1039137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44f7ba506ae2b4b361b9af006f42a47e783fc7f3371584561edd8c4bb07f9bcc" } } ], "extra": [ 1, 13, 206, 111, 158, 227, 55, 61, 79, 69, 241, 29, 139, 42, 42, 177, 154, 204, 231, 238, 167, 236, 124, 187, 255, 36, 42, 109, 186, 15, 170, 24, 152, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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