← previous blocknext block →recent activity
Analyzing
Block #86,698,031
11 transactions · 8 stateful · 2026-07-09 20:49:36 UTC
Parallelism
55/100
Blocked
50%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,698,031 · 11 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
2w03w14w26w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xe8a876d4…921a
0xb1dbf0…c0d3
4 touches
1 conflict
0x4af2cce5…16c4
0xb1dbf0…c0d3
4 touches
1 conflict
0x6286219a…0721
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d19c
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1a9
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1aa
0xb1dbf0…c0d3
4 touches
1 conflict
0x22e0cc1d…ad0d
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity