← previous blocknext block →recent activity
Analyzing
Block #87,880,364
22 transactions · 20 stateful · 2026-07-15 08:35:45 UTC
Parallelism
73/100
Blocked
65%
Avg conflicts / tx
1.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,880,364 · 22 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
1w02w15w06w17w28w39w411w112w213w314w115w416w517w220w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9f83113a…dcd8
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0xe4b8f2c5…f54d
0x34b655…2a6f
6 touches
3 conflicts
0x0dd44476…ef40
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x7ae195ed…3632
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
15 conflicts on slot 0x9f83113ae0…0edcd8
Audit this contract →
← previous block·next block →recent activity