Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e1455b58cb39da61b3810835e181d9baa82fb835ebcba32590c52bd73581844

Tx prefix hash: 4528987a8d4a0b337af283c26a118c0da874fd4fc167981ddb9881013252775a
Tx public key: 54e098ca6f7f4f74be6371346ff287f556f3883c823c6c9ecde25877236d8fce
Timestamp: 1580617345 Timestamp [UCT]: 2020-02-02 04:22:25 Age [y:d:h:m:s]: 04:298:02:18:19
Block: 56857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1104369 RingCT/type: yes/0
Extra: 0154e098ca6f7f4f74be6371346ff287f556f3883c823c6c9ecde25877236d8fce021100000001b221b3d1000000000000000000

1 output(s) for total of 397.756678727000 dcy

stealth address amount amount idx
00: 64d7573d496a77a195a89ae88f6026467c5641004a2b6db85a91e9f4ff562e98 397.756678727000 104846 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": 56867, "vin": [ { "gen": { "height": 56857 } } ], "vout": [ { "amount": 397756678727, "target": { "key": "64d7573d496a77a195a89ae88f6026467c5641004a2b6db85a91e9f4ff562e98" } } ], "extra": [ 1, 84, 224, 152, 202, 111, 127, 79, 116, 190, 99, 113, 52, 111, 242, 135, 245, 86, 243, 136, 60, 130, 60, 108, 158, 205, 226, 88, 119, 35, 109, 143, 206, 2, 17, 0, 0, 0, 1, 178, 33, 179, 209, 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