← previous blocknext block →recent activity
Analyzing
Block #87,787,339
12 transactions · 11 stateful · 2026-07-14 22:13:34 UTC
Parallelism
83/100
Blocked
45%
Avg conflicts / tx
0.42
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,787,339 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w17w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb236f3d1…6e04
0x34b655…2a6f
4 touches
1 conflict
0xf28082df…312c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x1aa1c24c…9514
0x34b655…2a6f
4 touches
1 conflict
0x3fde350e…8d43
0x34b655…2a6f
4 touches
1 conflict
0xe2263bea…6a9e
0x2b46c0…1669
2 touches
0 conflicts
0xe2263bea…6a9f
0x2b46c0…1669
2 touches
0 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
1 conflict on slot 0xb236f3d1d8…026e04
Audit this contract →
← previous block·next block →recent activity