← previous blocknext block →recent activity
Analyzing
Block #96,030,965
25 transactions · 22 stateful · 2026-08-14 22:00:29 UTC
Parallelism
68/100
Blocked
45%
Avg conflicts / tx
0.8
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,030,965 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w27w39w310w412w513w014w115w219w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x427c9fc4…5cee
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc10b903d…2f54
0x34b655…2a6f
6 touches
3 conflicts
0xcf3cb734…76b0
0x968279…9342
6 touches
3 conflicts
0xb4e0a934…5fc7
0x34b655…2a6f
6 touches
3 conflicts
0xa2fc1825…1af6
0x968279…9342
6 touches
3 conflicts
0xcf3cb734…76ad
0x968279…9342
6 touches
3 conflicts
0xcf3cb734…76ae
0x968279…9342
6 touches
3 conflicts
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 0x427c9fc46b…895cee
Audit this contract →
← previous block·next block →recent activity