← previous blocknext block →recent activity
Analyzing
Block #86,805,793
16 transactions · 11 stateful · 2026-07-10 08:49:24 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,805,793 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w06w27w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2264392…d5f4
0x34b655…2a6f
4 touches
1 conflict
0x8e516d08…05f3
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x94ba9c4a…41d8
0x34b655…2a6f
4 touches
1 conflict
0xbc7d5199…c05f
0x34b655…2a6f
4 touches
1 conflict
0xe1af7d74…7621
0x34b655…2a6f
4 touches
1 conflict
0xe1af7d74…7622
0x34b655…2a6f
4 touches
1 conflict
0x01df0928…3426
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
1 conflict on slot 0xe2264392ec…c0d5f4
Audit this contract →
← previous block·next block →recent activity