← previous blocknext block →recent activity
Analyzing
Block #96,033,756
24 transactions · 22 stateful · 2026-08-14 22:14:33 UTC
Parallelism
67/100
Blocked
68%
Avg conflicts / tx
1.92
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,033,756 · 24 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
1w02w13w04w15w26w37w38w49w510w613w418w519w120w221w223w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3a621f8…75a2
0x34b655…2a6f
14 touches
21 conflicts
0x4c188934…158e
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0x3464bbc5…a323
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x6fd9ae7c…e980
0x1b6862…e19c
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
21 conflicts on slot 0xa3a621f8f3…6975a2
Audit this contract →
← previous block·next block →recent activity