← previous blocknext block →recent activity
Analyzing
Block #95,123,050
24 transactions · 22 stateful · 2026-08-11 17:38:46 UTC
Parallelism
79/100
Blocked
45%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,123,050 · 24 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
1w02w14w27w08w19w210w312w014w217w319w421w022w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e638f1c…f1e4
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2c75ca93…a569
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x5a8d5be5…d9a4
0x34b655…2a6f
6 touches
3 conflicts
0x43fab434…896f
0xa6afd3…d132
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x366c7d57…0ed1
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
3 conflicts on slot 0x3e638f1c95…3ff1e4
Audit this contract →
← previous block·next block →recent activity