← previous blocknext block →recent activity
Analyzing
Block #86,126,788
11 transactions · 11 stateful · 2026-07-07 05:10:53 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,126,788 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea1b8c07…b969
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x172b0de5…980b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x74b66dfb…1ed4
0x34b655…2a6f
2 touches
0 conflicts
0x82dd99dd…a361
0x34b655…2a6f
2 touches
0 conflicts
0x9f60dbd0…5f36
0x34b655…2a6f
2 touches
0 conflicts
0xa8dbe7b0…8bad
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xea1b8c07ee…d0b969
Audit this contract →
← previous block·next block →recent activity