Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fa134d14cf93c5b0987ba4208cfcb92eeff504df666f4ee8b9258457410c2dc

Tx prefix hash: a74d412d74af10c514b0a4fa2e180a38904a28b504cdeb8ab41a0e500afa1db0
Tx public key: e1e9b8617eb5f301dda016af8579e73b4c2b80eb54cecf62466ced2f86fdd127
Timestamp: 1579677734 Timestamp [UCT]: 2020-01-22 07:22:14 Age [y:d:h:m:s]: 04:303:05:01:35
Block: 50786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106321 RingCT/type: yes/0
Extra: 01e1e9b8617eb5f301dda016af8579e73b4c2b80eb54cecf62466ced2f86fdd12702110000006217786bcf000000000000000000

1 output(s) for total of 416.606202551000 dcy

stealth address amount amount idx
00: ca57c46a34dce8ba824d8e29d12b703fbb48fd6f7ae8418a1273ef420c3f34d8 416.606202551000 94194 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": 50796, "vin": [ { "gen": { "height": 50786 } } ], "vout": [ { "amount": 416606202551, "target": { "key": "ca57c46a34dce8ba824d8e29d12b703fbb48fd6f7ae8418a1273ef420c3f34d8" } } ], "extra": [ 1, 225, 233, 184, 97, 126, 181, 243, 1, 221, 160, 22, 175, 133, 121, 231, 59, 76, 43, 128, 235, 84, 206, 207, 98, 70, 108, 237, 47, 134, 253, 209, 39, 2, 17, 0, 0, 0, 98, 23, 120, 107, 207, 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