← previous blocknext block →recent activity
Analyzing
Block #86,919,970
16 transactions · 12 stateful · 2026-07-10 21:32:51 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,919,970 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w07w28w310w415w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xd5c56995…6d21
0x34b655…2a6f
4 touches
1 conflict
0xd5c56995…6d22
0x34b655…2a6f
4 touches
1 conflict
0x48e6f054…d2ac
0x34b655…2a6f
4 touches
1 conflict
0xa1940963…fe97
0x34b655…2a6f
4 touches
1 conflict
0x7048d42f…288b
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity