← previous blocknext block →recent activity
Analyzing
Block #87,418,195
16 transactions · 15 stateful · 2026-07-13 05:03:54 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
1.5
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,418,195 · 16 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
3w04w15w26w37w49w010w111w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ca32a09…4e48
0x34b655…2a6f
14 touches
21 conflicts
0x79bdf655…91f2
0x34b655…2a6f
8 touches
6 conflicts
0x366f651e…6100
0x34b655…2a6f
8 touches
6 conflicts
0xc3227661…a8b3
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x8e5cc690…b06b
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
21 conflicts on slot 0x6ca32a096a…2c4e48
Audit this contract →
← previous block·next block →recent activity