Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42d4d10436885b5944fc47796a8f6b6c834f21a575eb809c66600421c40faedb

Tx prefix hash: 08a1bcf1e59fc3c34f9705ca4f75b5824d28bf86fd436c8fe91b3b1324b0fdfa
Tx public key: b628d9ada9b3e95bdc92d731427eb1cf0281006798ccdd6a49caa52c1b717c57
Timestamp: 1583956804 Timestamp [UCT]: 2020-03-11 20:00:04 Age [y:d:h:m:s]: 05:082:19:01:54
Block: 80816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1214889 RingCT/type: yes/0
Extra: 01b628d9ada9b3e95bdc92d731427eb1cf0281006798ccdd6a49caa52c1b717c570211000000224ac5aa02000000000000000000

1 output(s) for total of 331.301828206000 dcy

stealth address amount amount idx
00: 7e2a3d8a7a76addecd051c1956be4336503e31d3c43c86ffc3fde439a38acd71 331.301828206000 147838 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": 80826, "vin": [ { "gen": { "height": 80816 } } ], "vout": [ { "amount": 331301828206, "target": { "key": "7e2a3d8a7a76addecd051c1956be4336503e31d3c43c86ffc3fde439a38acd71" } } ], "extra": [ 1, 182, 40, 217, 173, 169, 179, 233, 91, 220, 146, 215, 49, 66, 126, 177, 207, 2, 129, 0, 103, 152, 204, 221, 106, 73, 202, 165, 44, 27, 113, 124, 87, 2, 17, 0, 0, 0, 34, 74, 197, 170, 2, 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