Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28bf67a8ac4766b5a7a73352ab41775d1b8a01ce73ed7dc67157b758907179d7

Tx prefix hash: f1a3e8cd3c5605f24b8bb79ab9050d260e357e7a1cf749dabe71162326865f83
Tx public key: ee10dc63c4dbf59d3da7e331618fba137ff3d3eabde3d132c9e5e818e61affd2
Timestamp: 1582026367 Timestamp [UCT]: 2020-02-18 11:46:07 Age [y:d:h:m:s]: 04:318:18:18:36
Block: 67337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1120338 RingCT/type: yes/0
Extra: 01ee10dc63c4dbf59d3da7e331618fba137ff3d3eabde3d132c9e5e818e61affd202110000000a4943cd9f000000000000000000

1 output(s) for total of 367.185373940000 dcy

stealth address amount amount idx
00: 529abec69a213e4e55f30584180c4095bb277039ceb7048f3c157c7531a21e2f 367.185373940000 124117 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": 67347, "vin": [ { "gen": { "height": 67337 } } ], "vout": [ { "amount": 367185373940, "target": { "key": "529abec69a213e4e55f30584180c4095bb277039ceb7048f3c157c7531a21e2f" } } ], "extra": [ 1, 238, 16, 220, 99, 196, 219, 245, 157, 61, 167, 227, 49, 97, 143, 186, 19, 127, 243, 211, 234, 189, 227, 209, 50, 201, 229, 232, 24, 230, 26, 255, 210, 2, 17, 0, 0, 0, 10, 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