← previous blocknext block →recent activity
Analyzing
Block #96,568,883
22 transactions · 20 stateful · 2026-08-16 19:06:21 UTC
Parallelism
68/100
Blocked
55%
Avg conflicts / tx
1.77
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,568,883 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w27w28w39w415w116w217w318w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
12 touches
15 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x29c1a140…099f
0x34b655…2a6f
8 touches
6 conflicts
0xde08e622…d1ce
0x34b655…2a6f
6 touches
3 conflicts
0x5e71af98…bfd6
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xa5a8ffca…8de2
0x34b655…2a6f
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
15 conflicts on slot 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity