← previous blocknext block →recent activity
Analyzing
Block #96,532,755
14 transactions · 12 stateful · 2026-08-16 16:04:39 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,532,755 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w311w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x201d7cf1…f7f2
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x784eaad2…d176
0x34b655…2a6f
6 touches
3 conflicts
0x41141440…bb96
0x34b655…2a6f
6 touches
3 conflicts
0x4acc6dca…a868
0x34b655…2a6f
5 touches
3 conflicts
0x87ab06cc…147e
0x34b655…2a6f
5 touches
3 conflicts
0xac2a0273…721b
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 0x201d7cf137…32f7f2
Audit this contract →
← previous block·next block →recent activity