Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06b7a08f0e20050f59bd2ccabc3cfed21a0ac6a054deb6e5f51f89c7aab82db0

Tx prefix hash: 96b5c92dbcceb88dfa668d3438388c4416211bb3fd92c8a966e6627be2f335e2
Tx public key: 771fbdb35011357c00089ed24f411cbff0dba4a6cdfcd17c29db29c565651f5a
Timestamp: 1580886289 Timestamp [UCT]: 2020-02-05 07:04:49 Age [y:d:h:m:s]: 05:247:22:01:40
Block: 58871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1327080 RingCT/type: yes/0
Extra: 01771fbdb35011357c00089ed24f411cbff0dba4a6cdfcd17c29db29c565651f5a02110000000217786bcf000000000000000000

1 output(s) for total of 391.684836199000 dcy

stealth address amount amount idx
00: 47058eb6d1f1f2e50ee261cdfd74ab5f4d830d6fe83d4b0704f7d8d17c6d63d2 391.684836199000 108799 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": 58881, "vin": [ { "gen": { "height": 58871 } } ], "vout": [ { "amount": 391684836199, "target": { "key": "47058eb6d1f1f2e50ee261cdfd74ab5f4d830d6fe83d4b0704f7d8d17c6d63d2" } } ], "extra": [ 1, 119, 31, 189, 179, 80, 17, 53, 124, 0, 8, 158, 210, 79, 65, 28, 191, 240, 219, 164, 166, 205, 252, 209, 124, 41, 219, 41, 197, 101, 101, 31, 90, 2, 17, 0, 0, 0, 2, 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