← previous blocknext block →recent activity
Analyzing
Block #95,204,367
17 transactions · 16 stateful · 2026-08-12 00:27:46 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,204,367 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w07w18w29w010w111w115w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
6 touches
3 conflicts
0x51232c8c…f30c
0xe52b14…7230
6 touches
3 conflicts
0xa6e37efb…afc0
0xe52b14…7230
6 touches
3 conflicts
0xa6e37efb…afc2
0xe52b14…7230
6 touches
3 conflicts
0x217bd767…b79e
0x34b655…2a6f
6 touches
3 conflicts
0x0b0c2e8d…c1b8
0xe52b14…7230
6 touches
3 conflicts
0xa8fa99e7…74fa
0xe52b14…7230
4 touches
3 conflicts
0x80afd9d9…57cf
0x065c9d…c394
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: 0xe52b1424…bb7230
3 conflicts on slot 0xf79df061c7…91e005
Audit this contract →
← previous block·next block →recent activity