← previous blocknext block →recent activity
Analyzing
Block #87,752,789
16 transactions · 14 stateful · 2026-07-14 18:22:25 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,752,789 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w08w19w210w214w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f20950e…df65
0x34b655…2a6f
6 touches
3 conflicts
0xe3f67d6c…a1aa
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x191c9934…f4f4
0x34b655…2a6f
4 touches
1 conflict
0x5ad347dc…ff16
0x34b655…2a6f
4 touches
1 conflict
0x7012fd2e…ae67
0x34b655…2a6f
4 touches
1 conflict
0x7012fd2e…ae68
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x0f20950e58…09df65
Audit this contract →
← previous block·next block →recent activity