Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 239a10ddc83b88161e92f22af686c893c567119afd81ac4bd2342625e73bb20c

Tx prefix hash: afa4a41389a882be3216247521ced6284c1131c42e0e2c4e3665c5683789b8c6
Tx public key: 5891992d549042143d1cec37d7e5497ef683e54b3f863a3a74f4fa9c4f6c776c
Timestamp: 1580974941 Timestamp [UCT]: 2020-02-06 07:42:21 Age [y:d:h:m:s]: 04:295:14:41:27
Block: 59543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1102869 RingCT/type: yes/0
Extra: 015891992d549042143d1cec37d7e5497ef683e54b3f863a3a74f4fa9c4f6c776c0211000000057adf42d3000000000000000000

1 output(s) for total of 389.705707842000 dcy

stealth address amount amount idx
00: 3e6374c68d85b66a88f2eed0510c4422c7b02fb49c006835f0c1ea4e89512fc3 389.705707842000 109959 of 0

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": 59553, "vin": [ { "gen": { "height": 59543 } } ], "vout": [ { "amount": 389705707842, "target": { "key": "3e6374c68d85b66a88f2eed0510c4422c7b02fb49c006835f0c1ea4e89512fc3" } } ], "extra": [ 1, 88, 145, 153, 45, 84, 144, 66, 20, 61, 28, 236, 55, 215, 229, 73, 126, 246, 131, 229, 75, 63, 134, 58, 58, 116, 244, 250, 156, 79, 108, 119, 108, 2, 17, 0, 0, 0, 5, 122, 223, 66, 211, 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