← previous blocknext block →recent activity
Analyzing
Block #87,331,642
22 transactions · 17 stateful · 2026-07-12 19:25:00 UTC
Parallelism
77/100
Blocked
53%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,331,642 · 22 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
1w02w16w07w18w211w314w415w216w118w019w120w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7013be2…c0a8
0x34b655…2a6f
10 touches
10 conflicts
0x52e69143…95ad
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x085df2c1…305a
0x34b655…2a6f
6 touches
3 conflicts
0x2b98be55…d0df
0x34b655…2a6f
6 touches
3 conflicts
0x30ded6ec…3424
0x34b655…2a6f
6 touches
3 conflicts
0x85a88798…f85e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
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 0xa7013be2a1…9ac0a8
Audit this contract →
← previous block·next block →recent activity