← previous blocknext block →recent activity
Analyzing
Block #83,666,302
22 transactions · 20 stateful · 2026-06-25 19:48:35 UTC
Parallelism
73/100
Blocked
45%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,666,302 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w09w210w311w414w015w116w518w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xec71d7fa…def3
0x34b655…2a6f
8 touches
6 conflicts
0xcc2cd268…5687
0x34b655…2a6f
6 touches
3 conflicts
0x8b305a3b…1c35
0x34b655…2a6f
6 touches
3 conflicts
0xc3464910…786f
0x34b655…2a6f
6 touches
3 conflicts
0x0a6cb118…4ca7
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity