← previous blocknext block →recent activity
Analyzing
Block #86,318,951
22 transactions · 18 stateful · 2026-07-08 02:34:00 UTC
Parallelism
91/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,318,951 · 22 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
6w07w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4fb37aa…5970
0x34b655…2a6f
4 touches
1 conflict
0xc108f63d…204f
0x34b655…2a6f
4 touches
1 conflict
0xca411fd0…9734
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5a9274d…78d7
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x3bdd71a2…b6eb
0x34b655…2a6f
4 touches
1 conflict
0x5cc231f5…f1cd
0x69df8a…6292
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 0xa4fb37aac5…245970
Audit this contract →
← previous block·next block →recent activity