← previous blocknext block →recent activity
Analyzing
Block #95,287,151
11 transactions · 9 stateful · 2026-08-12 07:33:06 UTC
Parallelism
64/100
Blocked
56%
Avg conflicts / tx
0.91
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,287,151 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w27w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x8d6a3425…d7e7
0x968279…9342
6 touches
3 conflicts
0x0d4eb15a…1ca1
0x968279…9342
6 touches
3 conflicts
0x0d4eb15a…1ca2
0x968279…9342
6 touches
3 conflicts
0x0d4eb15a…1ca4
0x968279…9342
6 touches
3 conflicts
0x8d6a3425…d7e0
0x968279…9342
6 touches
3 conflicts
0x8d6a3425…d7e1
0x968279…9342
6 touches
3 conflicts
0x8d6a3425…d7e4
0x968279…9342
6 touches
3 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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity