← previous blocknext block →recent activity
Analyzing
Block #86,331,188
18 transactions · 17 stateful · 2026-07-08 03:55:42 UTC
Parallelism
67/100
Blocked
35%
Avg conflicts / tx
0.44
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,331,188 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w09w213w114w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d537073…cf27
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x060aae4e…f1d0
0x34b655…2a6f
4 touches
1 conflict
0x0654b954…7285
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x6762cac2…3fb0
0x34b655…2a6f
4 touches
1 conflict
0x96047c45…b64a
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
3 conflicts on slot 0x5d537073f1…d2cf27
Audit this contract →
← previous block·next block →recent activity