← previous blocknext block →recent activity
Analyzing
Block #86,331,099
19 transactions · 14 stateful · 2026-07-08 03:55:06 UTC
Parallelism
68/100
Blocked
36%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,331,099 · 19 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
11w014w115w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x0d2de0f6…e6c6
0x34b655…2a6f
8 touches
6 conflicts
0xd8834cf3…0004
0x34b655…2a6f
6 touches
3 conflicts
0x5571e830…9cea
0x34b655…2a6f
6 touches
3 conflicts
0x3e583b1f…bc53
0x34b655…2a6f
6 touches
3 conflicts
0x483e2bf4…2b74
0x34b655…2a6f
4 touches
1 conflict
0x77cf3c7b…a722
0x34b655…2a6f
4 touches
1 conflict
0x747f609d…1555
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity