Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 885b01c8e39094025dc7c2ea952f0edcfb64222c9994e222d408a5aadfd61af5

Tx prefix hash: 7eda77a008560251a4a5b32a6e19e9194b634526910004f4fa95067bc9f39f18
Tx public key: 860127678f8759b9be1c4e5cc99d653ea4b9ffa4f85fe3dcaca7a67f1676c963
Timestamp: 1639562380 Timestamp [UCT]: 2021-12-15 09:59:40 Age [y:d:h:m:s]: 03:055:05:44:39
Block: 395976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 818203 RingCT/type: yes/0
Extra: 01860127678f8759b9be1c4e5cc99d653ea4b9ffa4f85fe3dcaca7a67f1676c963021100000001117daff0000000000000000000

1 output(s) for total of 29.920406658000 dcy

stealth address amount amount idx
00: 501aee4f17a42e267b90e7e757503845c660e22560af6efa2587036fadf87d70 29.920406658000 794083 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": 395986, "vin": [ { "gen": { "height": 395976 } } ], "vout": [ { "amount": 29920406658, "target": { "key": "501aee4f17a42e267b90e7e757503845c660e22560af6efa2587036fadf87d70" } } ], "extra": [ 1, 134, 1, 39, 103, 143, 135, 89, 185, 190, 28, 78, 92, 201, 157, 101, 62, 164, 185, 255, 164, 248, 95, 227, 220, 172, 167, 166, 127, 22, 118, 201, 99, 2, 17, 0, 0, 0, 1, 17, 125, 175, 240, 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