← previous blocknext block →recent activity
Analyzing
Block #87,513,232
49 transactions · 34 stateful · 2026-07-13 15:39:28 UTC
Parallelism
67/100
Blocked
59%
Avg conflicts / tx
2.18
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,513,232 · 49 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w010w011w112w213w314w415w516w617w718w819w920w1032w1134w235w1237w142w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0x69ce640b…884a
0x34b655…2a6f
12 touches
15 conflicts
0x4c04ce68…d007
0x34b655…2a6f
12 touches
15 conflicts
0x9365e097…ff56
0x34b655…2a6f
10 touches
10 conflicts
0x8cf1f868…c5af
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 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
55 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity