← previous blocknext block →recent activity
Analyzing
Block #87,731,062
32 transactions · 31 stateful · 2026-07-14 15:57:05 UTC
Parallelism
66/100
Blocked
55%
Avg conflicts / tx
1.69
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,731,062 · 32 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
2w03w04w15w06w17w08w19w210w311w412w513w616w122w227w728w829w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x9243d2e7…9c5d
0x34b655…2a6f
10 touches
10 conflicts
0xa55c4598…2988
0x34b655…2a6f
8 touches
6 conflicts
0xbf0e051a…10a0
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
6 touches
3 conflicts
0x0dd44476…ef40
0x34b655…2a6f
6 touches
3 conflicts
0x428b6e5b…8909
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity