← previous blocknext block →recent activity
Analyzing
Block #86,318,820
22 transactions · 20 stateful · 2026-07-08 02:33:07 UTC
Parallelism
86/100
Blocked
35%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,318,820 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w07w18w211w012w013w115w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8eb2d31…2ac0
0xea1b8e…c5ec
6 touches
3 conflicts
0xeef70cb9…5de7
0xea1b8e…c5ec
6 touches
3 conflicts
0xfecd05e7…296f
0xea1b8e…c5ec
6 touches
3 conflicts
0xfecd05e7…2970
0xea1b8e…c5ec
6 touches
3 conflicts
0x00bac013…a28c
0xfd44b3…00d1
6 touches
3 conflicts
0x9560013d…8caf
0xfd44b3…00d1
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0xfa2527aa…9dd5
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: LeverUp: LeverUp
3 conflicts on slot 0xd8eb2d31c2…a32ac0
Audit this contract →
← previous block·next block →recent activity