← previous blocknext block →recent activity
Analyzing
Block #85,131,272
22 transactions · 20 stateful · 2026-07-02 14:36:40 UTC
Parallelism
82/100
Blocked
35%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,131,272 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w07w18w29w012w118w019w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x05b1b07a…7a99
0x34b655…2a6f
4 touches
1 conflict
0x086b6103…b991
0x34b655…2a6f
4 touches
1 conflict
0x0d68fa12…4f04
0x34b655…2a6f
4 touches
1 conflict
0x587911c7…9e01
0x34b655…2a6f
4 touches
1 conflict
0x77cf3c7b…a722
0x34b655…2a6f
4 touches
1 conflict
0x7fffd49d…772a
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