← previous blocknext block →recent activity
Analyzing
Block #87,733,333
19 transactions · 17 stateful · 2026-07-14 16:12:17 UTC
Parallelism
68/100
Blocked
41%
Avg conflicts / tx
1.37
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,733,333 · 19 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
3w04w16w07w19w210w311w312w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa55c4598…2988
0x34b655…2a6f
10 touches
10 conflicts
0x067c61b8…650f
0x34b655…2a6f
10 touches
10 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
8 touches
6 conflicts
0x50718952…7c75
0x34b655…2a6f
8 touches
6 conflicts
0xf28cf8dc…b0ca
0x34b655…2a6f
6 touches
3 conflicts
0x0dd44476…ef40
0x34b655…2a6f
6 touches
3 conflicts
0x147259c6…1709
0x34b655…2a6f
6 touches
3 conflicts
0x49a97bff…33ed
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
10 conflicts on slot 0xa55c45989b…e52988
Audit this contract →
← previous block·next block →recent activity