← previous blocknext block →recent activity
Analyzing
Block #96,021,661
12 transactions · 9 stateful · 2026-08-14 21:13:41 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,021,661 · 12 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
4w05w16w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa321461b…36cf
0x34b655…2a6f
8 touches
6 conflicts
0x31616f97…1acc
0x34b655…2a6f
6 touches
3 conflicts
0x35c29640…8779
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x7f4a8466…f2cc
0x2b46c0…1669
2 touches
0 conflicts
0x5d7e0e69…e6d1
0x34b655…2a6f
2 touches
0 conflicts
0x5d7e0e69…e6d2
0x34b655…2a6f
2 touches
0 conflicts
0xcf8e8419…c691
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
6 conflicts on slot 0xa321461b05…6136cf
Audit this contract →
← previous block·next block →recent activity