Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0499fa3fa0e00a4a35673f38a9185c53f682747a7104a2cbb1180c2f47cc6b9e

Tx prefix hash: 2b86a62191e488023bdda264c44f39e0e7263a85cd30d73abe23bdc878a138e6
Tx public key: e929a29e509826b1f2ce40ea44b293067119684f50dde0fa3b9ab3bd00e1f534
Timestamp: 1579045514 Timestamp [UCT]: 2020-01-14 23:45:14 Age [y:d:h:m:s]: 04:173:19:59:06
Block: 45669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1013606 RingCT/type: yes/0
Extra: 01e929a29e509826b1f2ce40ea44b293067119684f50dde0fa3b9ab3bd00e1f5340211000000072264afe6000000000000000000

1 output(s) for total of 433.199526413000 dcy

stealth address amount amount idx
00: 140077148c0c2fa43a59d295462e86036f066fbbeacebb6d11bb45b01f6b9eca 433.199526413000 83575 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": 45679, "vin": [ { "gen": { "height": 45669 } } ], "vout": [ { "amount": 433199526413, "target": { "key": "140077148c0c2fa43a59d295462e86036f066fbbeacebb6d11bb45b01f6b9eca" } } ], "extra": [ 1, 233, 41, 162, 158, 80, 152, 38, 177, 242, 206, 64, 234, 68, 178, 147, 6, 113, 25, 104, 79, 80, 221, 224, 250, 59, 154, 179, 189, 0, 225, 245, 52, 2, 17, 0, 0, 0, 7, 34, 100, 175, 230, 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