← previous blocknext block →recent activity
Analyzing
Block #95,426,082
19 transactions · 18 stateful · 2026-08-12 19:16:32 UTC
Parallelism
74/100
Blocked
33%
Avg conflicts / tx
0.84
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,426,082 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w17w28w39w210w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7d36805…6bb8
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd2090360…7b89
0x34b655…2a6f
6 touches
3 conflicts
0x620b761c…270e
0x34b655…2a6f
6 touches
3 conflicts
0x4f394483…ff62
0x34b655…2a6f
4 touches
1 conflict
0xbcdd58ff…0711
0x34b655…2a6f
4 touches
1 conflict
0x5da59c2b…d7b2
0x34b655…2a6f
4 touches
1 conflict
0x706c758c…2fdb
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
10 conflicts on slot 0xa7d368051f…dc6bb8
Audit this contract →
← previous block·next block →recent activity