← previous blocknext block →recent activity
Analyzing
Block #86,288,252
25 transactions · 20 stateful · 2026-07-07 23:08:53 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.32
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,288,252 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w113w022w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6637e421…af93
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x11560115…bfc2
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x0d488000…3831
0x34b655…2a6f
4 touches
1 conflict
0xe5e7089a…fb91
0x34b655…2a6f
4 touches
1 conflict
0x85167706…718e
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
6 conflicts on slot 0x6637e421bf…b0af93
Audit this contract →
← previous block·next block →recent activity