← previous blocknext block →recent activity
Analyzing
Block #86,855,207
14 transactions · 9 stateful · 2026-07-10 14:19:51 UTC
Parallelism
64/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,855,207 · 14 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
4w09w110w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x1911fbd1…f1bf
0x34b655…2a6f
4 touches
1 conflict
0x19292fad…ec5b
0x34b655…2a6f
4 touches
1 conflict
0x1941b441…5889
0x34b655…2a6f
4 touches
1 conflict
0x1ab6ab11…5bd9
0x34b655…2a6f
4 touches
1 conflict
0x1cbd009b…629b
0x34b655…2a6f
4 touches
1 conflict
0x3133f94b…f76b
0x34b655…2a6f
4 touches
1 conflict
0x350e5d8a…601f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity