← previous blocknext block →recent activity
Analyzing
Block #95,387,274
10 transactions · 9 stateful · 2026-08-12 16:00:15 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,387,274 · 10 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66d5e476…8a1f
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2130f288…281f
0x34b655…2a6f
2 touches
0 conflicts
0x43fd3667…094b
0x34b655…2a6f
2 touches
0 conflicts
0x444eb03f…15d7
0x34b655…2a6f
2 touches
0 conflicts
0x49c03b0b…e048
0x34b655…2a6f
2 touches
0 conflicts
0x4ab3c95f…ceb7
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 0x66d5e476c0…268a1f
Audit this contract →
← previous block·next block →recent activity