← previous blocknext block →recent activity
Analyzing
Block #96,512,507
17 transactions · 16 stateful · 2026-08-16 14:22:49 UTC
Parallelism
53/100
Blocked
50%
Avg conflicts / tx
1.47
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,512,507 · 17 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
1w03w14w25w36w48w010w512w613w716w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
12 touches
15 conflicts
0x4c4b7a66…c877
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x91cdfdeb…7feb
0x34b655…2a6f
6 touches
3 conflicts
0xa5a8ffca…8de2
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity