← previous blocknext block →recent activity
Analyzing
Block #86,620,191
13 transactions · 12 stateful · 2026-07-09 12:08:37 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,620,191 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c7e1952…d9c9
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1a8
0xb1dbf0…c0d3
4 touches
1 conflict
0x1941b441…5889
0x34b655…2a6f
4 touches
1 conflict
0x48c5af20…ceea
0xb1dbf0…c0d3
3 touches
1 conflict
0x64fccc04…8eab
0xb1dbf0…c0d3
3 touches
1 conflict
0x8a35acfb…d1a9
0xb1dbf0…c0d3
3 touches
1 conflict
0x30c49a82…39cf
0x34b655…2a6f
2 touches
0 conflicts
0x5f72d58f…c445
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x6c7e195218…27d9c9
Audit this contract →
← previous block·next block →recent activity