← previous blocknext block →recent activity
Analyzing
Block #86,969,941
10 transactions · 10 stateful · 2026-07-11 03:06:50 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,969,941 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00c39b26…3e0d
0x34b655…2a6f
4 touches
1 conflict
0x06aed19e…ca57
0x34b655…2a6f
4 touches
1 conflict
0x0b202b66…0409
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x36830c8a…c0b7
0x34b655…2a6f
4 touches
1 conflict
0x511ecf07…8ed0
0x34b655…2a6f
4 touches
1 conflict
0x6fe49da2…fd6f
0x34b655…2a6f
4 touches
1 conflict
0x727fbce7…0c80
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 0x00c39b2685…e03e0d
Audit this contract →
← previous block·next block →recent activity