← previous blocknext block →recent activity
Analyzing
Block #86,488,801
23 transactions · 23 stateful · 2026-07-08 21:29:03 UTC
Parallelism
65/100
Blocked
35%
Avg conflicts / tx
1.22
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,488,801 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w411w012w118w519w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
14 touches
21 conflicts
0x59dccbd8…2bf6
0x34b655…2a6f
10 touches
10 conflicts
0xf06c2cf5…61bd
0x34b655…2a6f
10 touches
10 conflicts
0xe45167d0…c16c
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2fdfe038…c16c
0x34b655…2a6f
6 touches
3 conflicts
0x9cddb1b1…c504
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
21 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity