← previous blocknext block →recent activity
Analyzing
Block #86,909,001
14 transactions · 13 stateful · 2026-07-10 20:19:38 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,909,001 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w212w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02c4bb0f…f2c8
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x74888025…a5b8
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x27934186…3779
0x34b655…2a6f
4 touches
1 conflict
0x2c0b7398…5fdb
0x34b655…2a6f
4 touches
1 conflict
0x5fee1ba0…2520
0x34b655…2a6f
4 touches
1 conflict
0x650e4fd3…956e
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 0x02c4bb0f0a…d0f2c8
Audit this contract →
← previous block·next block →recent activity