← previous blocknext block →recent activity
Analyzing
Block #87,577,428
20 transactions · 18 stateful · 2026-07-13 22:49:31 UTC
Parallelism
65/100
Blocked
61%
Avg conflicts / tx
1.45
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,577,428 · 20 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
1w02w13w04w05w16w27w38w410w011w112w514w615w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xdb7c435f…f490
0x34b655…2a6f
10 touches
10 conflicts
0xed81556c…ab0a
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
8 touches
6 conflicts
0x07f69062…03ec
0x34b655…2a6f
8 touches
6 conflicts
0x72707533…4cfb
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x826664fe…acfc
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity