← previous blocknext block →recent activity
Analyzing
Block #87,881,048
20 transactions · 19 stateful · 2026-07-15 08:40:19 UTC
Parallelism
70/100
Blocked
58%
Avg conflicts / tx
1.4
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,881,048 · 20 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
4w05w17w28w39w010w111w212w313w414w415w518w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0002
0x019883…2a9a
10 touches
10 conflicts
0x00000000…0003
0x019883…2a9a
10 touches
10 conflicts
0x44ad89ba…cf83
0x0cc9b2…7777
10 touches
10 conflicts
0x99a3a7c1…1e2b
0x0cc9b2…7777
10 touches
10 conflicts
0xa472d565…9fe4
0x3bd359…433a
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xa10c86f8…4b74
0x3bd359…433a
10 touches
10 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
15 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity