← previous blocknext block →recent activity
Analyzing
Block #86,791,437
11 transactions · 6 stateful · 2026-07-10 07:13:27 UTC
Parallelism
82/100
Blocked
33%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,791,437 · 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
3w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5767fdec…d9d4
0x34b655…2a6f
4 touches
1 conflict
0xc3688185…9b36
0x34b655…2a6f
4 touches
1 conflict
0x24ed74ea…a3ff
0x34b655…2a6f
4 touches
1 conflict
0x1bfc029c…f91e
0x34b655…2a6f
2 touches
0 conflicts
0x23aeaf0e…cfa6
0x34b655…2a6f
2 touches
0 conflicts
0x4caf91f9…8ab5
0x34b655…2a6f
2 touches
0 conflicts
0x6d99ac64…0aa3
0x34b655…2a6f
2 touches
0 conflicts
0x85a88798…f85e
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 0x5767fdeca9…38d9d4
Audit this contract →
← previous block·next block →recent activity