← previous blocknext block →recent activity
Analyzing
Block #87,487,159
17 transactions · 16 stateful · 2026-07-13 12:44:57 UTC
Parallelism
59/100
Blocked
50%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,487,159 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w06w17w28w310w412w513w114w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x521f03f8…dc0e
0x34b655…2a6f
10 touches
10 conflicts
0xe2c66a2e…150f
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x44f26862…4555
0x34b655…2a6f
6 touches
3 conflicts
0x4ca81ae8…01d4
0x34b655…2a6f
6 touches
3 conflicts
0x56b580bf…f969
0x34b655…2a6f
6 touches
3 conflicts
0x617c9740…a90e
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity