← previous blocknext block →recent activity
Analyzing
Block #95,021,998
19 transactions · 18 stateful · 2026-08-11 09:09:39 UTC
Parallelism
84/100
Blocked
39%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,021,998 · 19 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
1w02w13w04w16w29w112w213w217w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x278676c0…d15c
0x34b655…2a6f
6 touches
3 conflicts
0xe85638e6…207a
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x38c6ff01…689f
0x34b655…2a6f
4 touches
1 conflict
0x3b689fd2…629c
0x34b655…2a6f
4 touches
1 conflict
0x42adfa6a…b6bc
0x34b655…2a6f
4 touches
1 conflict
0x45ea7a97…bbb3
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0x278676c021…32d15c
Audit this contract →
← previous block·next block →recent activity