Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 023efc0cef3bd9a6f7097302c4cc0a3c23d80b611d78d9cf0012246293fcd862

Tx prefix hash: e53b8356581efc0adf00e310dc17c27bedec7e1aedabe4a23f7fcec7518141e8
Tx public key: 7f32058dd4a9ca71e1c838eb1a6269a02df739834c778a9fbbb2fc25d70509c3
Timestamp: 1582051510 Timestamp [UCT]: 2020-02-18 18:45:10 Age [y:d:h:m:s]: 05:059:08:57:42
Block: 67696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1195463 RingCT/type: yes/0
Extra: 017f32058dd4a9ca71e1c838eb1a6269a02df739834c778a9fbbb2fc25d70509c30211000000064943cd9f000000000000000000

1 output(s) for total of 366.181042796000 dcy

stealth address amount amount idx
00: 2050ae49fab0571974ac8afed65c2c1b9d919f06824be59a83d346f385c273ef 366.181042796000 124675 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": 67706, "vin": [ { "gen": { "height": 67696 } } ], "vout": [ { "amount": 366181042796, "target": { "key": "2050ae49fab0571974ac8afed65c2c1b9d919f06824be59a83d346f385c273ef" } } ], "extra": [ 1, 127, 50, 5, 141, 212, 169, 202, 113, 225, 200, 56, 235, 26, 98, 105, 160, 45, 247, 57, 131, 76, 119, 138, 159, 187, 178, 252, 37, 215, 5, 9, 195, 2, 17, 0, 0, 0, 6, 73, 67, 205, 159, 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