← previous blocknext block →recent activity
Analyzing
Block #86,776,420
16 transactions · 13 stateful · 2026-07-10 05:33:16 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,776,420 · 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
1w02w13w26w08w39w410w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7b8bfda…efc0
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x5303bbe2…aac6
0x851145…3f07
4 touches
1 conflict
0xae901867…8085
0x34b655…2a6f
4 touches
1 conflict
0xae901867…8086
0x34b655…2a6f
4 touches
1 conflict
0xc61f831e…e236
0x34b655…2a6f
4 touches
1 conflict
0xda16e95c…521b
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 0xb7b8bfda42…d1efc0
Audit this contract →
← previous block·next block →recent activity