← previous blocknext block →recent activity
Analyzing
Block #87,420,806
16 transactions · 15 stateful · 2026-07-13 05:21:20 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,420,806 · 16 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
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x6083af24…a0df
0x34b655…2a6f
4 touches
1 conflict
0x9c87f480…4fbf
0x34b655…2a6f
4 touches
1 conflict
0xa15e2d91…025a
0x34b655…2a6f
4 touches
1 conflict
0xb5f244d5…f550
0x34b655…2a6f
2 touches
0 conflicts
0xee8237bd…46ad
0x34b655…2a6f
2 touches
0 conflicts
0x07b979bc…3564
0xb1dbf0…c0d3
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity