← previous blocknext block →recent activity
Analyzing
Block #87,750,419
24 transactions · 23 stateful · 2026-07-14 18:06:35 UTC
Parallelism
79/100
Blocked
26%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,750,419 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w09w110w212w314w416w019w022w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x819b5176…86cf
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2a00a910…f960
0x34b655…2a6f
4 touches
1 conflict
0x366c7d57…0ed1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x55c2c22c…0474
0x34b655…2a6f
4 touches
1 conflict
0x6b59fc10…0d93
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
6 conflicts on slot 0x819b5176e8…3486cf
Audit this contract →
← previous block·next block →recent activity