← previous blocknext block →recent activity
Analyzing
Block #95,566,966
20 transactions · 18 stateful · 2026-08-13 07:05:09 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,566,966 · 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
2w03w14w08w09w110w013w216w217w319w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c6faea5…fa7f
0x34b655…2a6f
6 touches
3 conflicts
0x2bcdd4a1…3d3a
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x2df6f59b…d662
0x34b655…2a6f
4 touches
1 conflict
0x455a8076…be99
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x502b2bfa…410b
0x34b655…2a6f
4 touches
1 conflict
0x548491bd…1259
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 0x4c6faea5ac…fffa7f
Audit this contract →
← previous block·next block →recent activity