← previous blocknext block →recent activity
Analyzing
Block #95,009,023
13 transactions · 11 stateful · 2026-08-11 08:04:22 UTC
Parallelism
85/100
Blocked
18%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,009,023 · 13 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
1w02w14w05w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd08098a8…f0a6
0x34b655…2a6f
4 touches
1 conflict
0x86537543…cf99
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd6
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x5111cbd9…01fd
0x34b655…2a6f
2 touches
0 conflicts
0x5975ae58…89b0
0x34b655…2a6f
2 touches
0 conflicts
0x5e17e5be…d212
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
1 conflict on slot 0xd08098a893…b9f0a6
Audit this contract →
← previous block·next block →recent activity