← previous blocknext block →recent activity
Analyzing
Block #95,151,926
20 transactions · 19 stateful · 2026-08-11 20:04:01 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,151,926 · 20 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
1w02w13w04w15w210w311w013w114w216w117w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x424934c8…f2f1
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xfc24540b…6463
0x34b655…2a6f
4 touches
1 conflict
0x4984f7be…d515
0x34b655…2a6f
4 touches
1 conflict
0x966e45cf…0f25
0x34b655…2a6f
4 touches
1 conflict
0x8cd684d0…c3cb
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
6 conflicts on slot 0x424934c865…4af2f1
Audit this contract →
← previous block·next block →recent activity