Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dffdd65cfff31ffa96949701c4ed510a880bc483d1193533da95739093032bc

Tx prefix hash: 07679fb5e6e618b5a7e444e118f4ced943cf48595fb55f8422546eb4345c5820
Tx public key: 500f1136b6944baf8ff9212ec8dea8a2b7594cc8b0dc2fb44e30cdcb9af9cc88
Timestamp: 1583034160 Timestamp [UCT]: 2020-03-01 03:42:40 Age [y:d:h:m:s]: 05:004:04:39:44
Block: 74424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1157407 RingCT/type: yes/0
Extra: 01500f1136b6944baf8ff9212ec8dea8a2b7594cc8b0dc2fb44e30cdcb9af9cc8802110000007312c4732d000000000000000000

1 output(s) for total of 347.858957627000 dcy

stealth address amount amount idx
00: 6c5c35ac4e8d7b934c5f7d1405a4973ef13a88a34e8e119f1771c43902e94ef8 347.858957627000 137736 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": 74434, "vin": [ { "gen": { "height": 74424 } } ], "vout": [ { "amount": 347858957627, "target": { "key": "6c5c35ac4e8d7b934c5f7d1405a4973ef13a88a34e8e119f1771c43902e94ef8" } } ], "extra": [ 1, 80, 15, 17, 54, 182, 148, 75, 175, 143, 249, 33, 46, 200, 222, 168, 162, 183, 89, 76, 200, 176, 220, 47, 180, 78, 48, 205, 203, 154, 249, 204, 136, 2, 17, 0, 0, 0, 115, 18, 196, 115, 45, 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