← previous blocknext block →recent activity
Analyzing
Block #95,009,045
20 transactions · 17 stateful · 2026-08-11 08:04:28 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,009,045 · 20 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
1w02w13w25w06w18w09w112w213w314w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x000bde1a…e123
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x2e1f5171…ad2d
0x34b655…2a6f
6 touches
3 conflicts
0x7bf1c03f…c440
0x34b655…2a6f
6 touches
3 conflicts
0x6f97afda…faec
0x34b655…2a6f
6 touches
3 conflicts
0xd4a82208…0074
0xd32edf…ff58
5 touches
3 conflicts
0x3d22c439…de6d
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity