← previous blocknext block →recent activity
Analyzing
Block #95,202,838
18 transactions · 17 stateful · 2026-08-12 00:20:05 UTC
Parallelism
67/100
Blocked
41%
Avg conflicts / tx
1.22
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,202,838 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w06w27w38w410w011w312w517w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x424934c8…f2f1
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xf5ea108a…dbf6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd8bd73f8…27d6
0x34b655…2a6f
4 touches
1 conflict
0x0672e4a2…8d1f
0x34b655…2a6f
4 touches
1 conflict
0x3fff7ccd…5a48
0x34b655…2a6f
4 touches
1 conflict
0x5a19ef35…dc70
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 0x424934c865…4af2f1
Audit this contract →
← previous block·next block →recent activity