← previous blocknext block →recent activity
Analyzing
Block #94,913,286
24 transactions · 20 stateful · 2026-08-11 00:02:50 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,913,286 · 24 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
2w03w14w15w28w09w312w013w116w221w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x840d3ab7…c8c4
0x34b655…2a6f
8 touches
6 conflicts
0x734ee320…caae
0x34b655…2a6f
8 touches
6 conflicts
0x589623ea…8ce2
0x34b655…2a6f
6 touches
3 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
4 touches
1 conflict
0x1d946063…ba90
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x3cb4b659…f735
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x840d3ab7c3…edc8c4
Audit this contract →
← previous block·next block →recent activity