← previous blocknext block →recent activity
Analyzing
Block #87,444,075
17 transactions · 13 stateful · 2026-07-13 07:56:52 UTC
Parallelism
65/100
Blocked
54%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,444,075 · 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
2w05w16w27w39w412w514w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc99e7125…81b1
0x34b655…2a6f
8 touches
6 conflicts
0x67d8b378…f2f8
0x34b655…2a6f
8 touches
6 conflicts
0xfa213e57…62b4
0x34b655…2a6f
6 touches
3 conflicts
0x5170a218…3a84
0xc8689a…ee79
6 touches
3 conflicts
0x43738f23…b864
0x34b655…2a6f
6 touches
3 conflicts
0x587911c7…9e01
0x34b655…2a6f
6 touches
3 conflicts
0x67bfbc55…7b2f
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
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
6 conflicts on slot 0xc99e71253c…e381b1
Audit this contract →
← previous block·next block →recent activity