← previous blocknext block →recent activity
Analyzing
Block #87,638,187
20 transactions · 19 stateful · 2026-07-14 05:35:52 UTC
Parallelism
55/100
Blocked
47%
Avg conflicts / tx
1.55
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #87,638,187 · 20 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w511w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5a3b1be…8122
0x34b655…2a6f
16 touches
28 conflicts
0x5b145de0…367c
0xc8689a…ee79
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x8981596f…d14a
0x34b655…2a6f
12 touches
15 conflicts
0x9599eb41…b5d6
0x34b655…2a6f
12 touches
15 conflicts
0xaf65c4a2…4000
0x34b655…2a6f
12 touches
15 conflicts
0xcc6e2e88…6569
0x34b655…2a6f
12 touches
15 conflicts
0xd19c9d38…b459
0x34b655…2a6f
12 touches
15 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
28 conflicts on slot 0xb5a3b1be7c…288122
Audit this contract →
← previous block·next block →recent activity