← previous blocknext block →recent activity
Analyzing
Block #96,600,879
12 transactions · 10 stateful · 2026-08-16 21:47:17 UTC
Parallelism
58/100
Blocked
40%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,600,879 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d651956…12e8
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x5ef698c5…5ce4
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x2364dac9…7a56
0x34b655…2a6f
2 touches
0 conflicts
0x2d5e2e86…5fcd
0x34b655…2a6f
2 touches
0 conflicts
0x40128d8b…37af
0x34b655…2a6f
2 touches
0 conflicts
0x41cf2be3…59a0
0x34b655…2a6f
2 touches
0 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
10 conflicts on slot 0x2d65195682…4112e8
Audit this contract →
← previous block·next block →recent activity