← previous blocknext block →recent activity
Analyzing
Block #95,153,088
13 transactions · 13 stateful · 2026-08-11 20:09:51 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,153,088 · 13 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
2w04w05w16w28w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0672e4a2…8d1f
0x34b655…2a6f
6 touches
3 conflicts
0xac51e79f…cb9d
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xbfb4b02a…4b47
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x2afbb327…04fd
0x34b655…2a6f
2 touches
0 conflicts
0x4a2afb00…a2a8
0x34b655…2a6f
2 touches
0 conflicts
0x5d036786…b92e
0x34b655…2a6f
2 touches
0 conflicts
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 0x0672e4a279…2f8d1f
Audit this contract →
← previous block·next block →recent activity