← previous blocknext block →recent activity
Analyzing
Block #87,732,375
17 transactions · 16 stateful · 2026-07-14 16:05:52 UTC
Parallelism
65/100
Blocked
63%
Avg conflicts / tx
1.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,732,375 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w48w09w110w211w312w513w115w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
8 touches
6 conflicts
0xc4de6652…13f4
0x34b655…2a6f
8 touches
6 conflicts
0x84d74093…7808
0x34b655…2a6f
8 touches
6 conflicts
0x0dd44476…ef40
0x34b655…2a6f
8 touches
6 conflicts
0x5e4b65e1…ebe1
0x34b655…2a6f
7 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity