← previous blocknext block →recent activity
Analyzing
Block #87,046,044
22 transactions · 21 stateful · 2026-07-11 11:35:22 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,046,044 · 22 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
2w04w05w16w29w310w411w519w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x3b787279…727f
0x34b655…2a6f
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x0d43cc69…6f83
0x34b655…2a6f
8 touches
6 conflicts
0x5a65207b…4f30
0x34b655…2a6f
6 touches
3 conflicts
0x5b37bb6b…aaff
0x34b655…2a6f
6 touches
3 conflicts
0x5b37bb6b…ab00
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity