← previous blocknext block →recent activity
Analyzing
Block #95,193,817
22 transactions · 19 stateful · 2026-08-11 23:34:42 UTC
Parallelism
82/100
Blocked
47%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,193,817 · 22 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
2w03w14w05w18w09w110w211w213w315w016w120w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b179be5…a40a
0x34b655…2a6f
8 touches
6 conflicts
0x966e45cf…0f25
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xa5811d93…8c73
0x34b655…2a6f
6 touches
3 conflicts
0x151c62bc…6dd9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbba9dcbb…e4c9
0x34b655…2a6f
6 touches
3 conflicts
0x6b267bdf…b173
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 0x7b179be5f1…1ea40a
Audit this contract →
← previous block·next block →recent activity