← previous blocknext block →recent activity
Analyzing
Block #87,713,949
18 transactions · 15 stateful · 2026-07-14 14:02:28 UTC
Parallelism
61/100
Blocked
47%
Avg conflicts / tx
0.56
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,713,949 · 18 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
2w03w14w010w111w212w313w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x909b34ee…b9e3
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x95c2cdec…c059
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
4 touches
1 conflict
0x9cea6ca2…570e
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x909b34ee23…ddb9e3
Audit this contract →
← previous block·next block →recent activity