← previous blocknext block →recent activity
Analyzing
Block #83,633,861
28 transactions · 19 stateful · 2026-06-25 16:12:09 UTC
Parallelism
86/100
Blocked
37%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,633,861 · 28 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
5w06w19w012w013w114w115w219w020w125w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf997c4c7…617d
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0xcb89a818…e7c1
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xd79c9727…1233
0x34b655…2a6f
6 touches
3 conflicts
0x4bdcc5ee…7e90
0x34b655…2a6f
5 touches
3 conflicts
0x8f4c5cb2…cbee
0x34b655…2a6f
5 touches
3 conflicts
0x785889c9…0603
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
3 conflicts on slot 0xf997c4c76f…f2617d
Audit this contract →
← previous block·next block →recent activity