← previous blocknext block →recent activity
Analyzing
Block #87,587,044
21 transactions · 19 stateful · 2026-07-13 23:53:49 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,587,044 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w09w111w213w114w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x745952b2…d90c
0x34b655…2a6f
8 touches
6 conflicts
0x1baca9c3…2b23
0x34b655…2a6f
8 touches
6 conflicts
0x2b5101ac…090b
0x34b655…2a6f
8 touches
6 conflicts
0xf5adc2ae…ac32
0x34b655…2a6f
6 touches
3 conflicts
0xfcea0c54…587f
0x34b655…2a6f
6 touches
3 conflicts
0x3560a56c…d95d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
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
6 conflicts on slot 0x745952b2a0…a6d90c
Audit this contract →
← previous block·next block →recent activity