Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0362b6a19ff15056d74b112972879e33f1f74b3c99284497c44e2539d5fceab9

Tx prefix hash: d3fd286c45268cf779fefdf25aaa26dc30dfee21827eab4614b5fa8117ae173a
Tx public key: 8eac9f32cb49f6a43a676e8c51a860a35da0a61b45f10498c7ce18236bc08e1b
Timestamp: 1682769070 Timestamp [UCT]: 2023-04-29 11:51:10 Age [y:d:h:m:s]: 01:264:15:12:50
Block: 749139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450608 RingCT/type: yes/0
Extra: 018eac9f32cb49f6a43a676e8c51a860a35da0a61b45f10498c7ce18236bc08e1b0211000000017e406890000000000000000000

1 output(s) for total of 2.022049184000 dcy

stealth address amount amount idx
00: c2be28bd108168cd1cac2b970d8ce7800304cf6eebd2e46286cfd61a777d0201 2.022049184000 1197076 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": 749149, "vin": [ { "gen": { "height": 749139 } } ], "vout": [ { "amount": 2022049184, "target": { "key": "c2be28bd108168cd1cac2b970d8ce7800304cf6eebd2e46286cfd61a777d0201" } } ], "extra": [ 1, 142, 172, 159, 50, 203, 73, 246, 164, 58, 103, 110, 140, 81, 168, 96, 163, 93, 160, 166, 27, 69, 241, 4, 152, 199, 206, 24, 35, 107, 192, 142, 27, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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