← previous blocknext block →recent activity
Analyzing
Block #87,731,584
19 transactions · 18 stateful · 2026-07-14 16:00:34 UTC
Parallelism
42/100
Blocked
61%
Avg conflicts / tx
2.37
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,731,584 · 19 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w510w611w712w817w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x5b145de0…367c
0xc8689a…ee79
14 touches
21 conflicts
0x67905f6e…02a1
0x34b655…2a6f
14 touches
21 conflicts
0x747f609d…1555
0x34b655…2a6f
14 touches
21 conflicts
0xa55c4598…2988
0x34b655…2a6f
14 touches
21 conflicts
0xaa643d44…2122
0x34b655…2a6f
14 touches
21 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
14 touches
21 conflicts
0x2f461725…5ab2
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity