← previous blocknext block →recent activity
Analyzing
Block #96,520,190
12 transactions · 8 stateful · 2026-08-16 15:01:27 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,520,190 · 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
1w02w15w26w37w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7aad02c6…b979
0x34b655…2a6f
8 touches
6 conflicts
0x3f0a88e0…392e
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0xf4c9a0df…dcd4
0x34b655…2a6f
8 touches
6 conflicts
0x1a5d321d…a474
0x34b655…2a6f
6 touches
3 conflicts
0x4f9a134d…2c11
0x34b655…2a6f
4 touches
1 conflict
0x5ddcdf38…2135
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
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
6 conflicts on slot 0x7aad02c682…feb979
Audit this contract →
← previous block·next block →recent activity