← previous blocknext block →recent activity
Analyzing
Block #87,305,401
16 transactions · 14 stateful · 2026-07-12 16:29:30 UTC
Parallelism
63/100
Blocked
64%
Avg conflicts / tx
1.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,305,401 · 16 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
2w04w15w26w37w48w510w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64aaadbf…f9f3
0x34b655…2a6f
12 touches
15 conflicts
0xb35e663e…354e
0x34b655…2a6f
12 touches
15 conflicts
0x4ff21e31…8ed4
0x34b655…2a6f
10 touches
10 conflicts
0x7c7eff13…16db
0x34b655…2a6f
10 touches
10 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
10 touches
10 conflicts
0x434b7839…d546
0x34b655…2a6f
10 touches
10 conflicts
0xa112f315…1a92
0x34b655…2a6f
10 touches
10 conflicts
0xa5ab7b8a…c97b
0x34b655…2a6f
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 0x64aaadbf0a…79f9f3
Audit this contract →
← previous block·next block →recent activity