← previous blocknext block →recent activity
Analyzing
Block #87,794,192
16 transactions · 15 stateful · 2026-07-14 22:59:24 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,794,192 · 16 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
1w02w13w24w07w08w19w110w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8620c47a…99dc
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x82cb9f9d…f040
0xd32edf…ff58
5 touches
3 conflicts
0x4681609f…6493
0x34b655…2a6f
4 touches
1 conflict
0x75275ca5…ca83
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x9465204c…bf37
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 0x8620c47aa3…7d99dc
Audit this contract →
← previous block·next block →recent activity