← previous blocknext block →recent activity
Analyzing
Block #83,641,337
20 transactions · 17 stateful · 2026-06-25 17:02:06 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,641,337 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w17w210w012w013w114w119w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda5e0705…ecb9
0x34b655…2a6f
8 touches
6 conflicts
0x8ae827f1…aa36
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0x1951ee47…540f
0x34b655…2a6f
4 touches
1 conflict
0x225abf0c…8a6e
0x34b655…2a6f
4 touches
1 conflict
0x4f62463a…d390
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 0xda5e0705c4…a5ecb9
Audit this contract →
← previous block·next block →recent activity