← previous blocknext block →recent activity
Analyzing
Block #96,543,381
11 transactions · 11 stateful · 2026-08-16 16:58:05 UTC
Parallelism
55/100
Blocked
36%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,543,381 · 11 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17f5dec8…3332
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x427d1120…4eb1
0x34b655…2a6f
6 touches
3 conflicts
0xea2a9764…868b
0x34b655…2a6f
4 touches
1 conflict
0x17c40594…7e17
0x34b655…2a6f
4 touches
1 conflict
0x28f324ed…9db7
0x34b655…2a6f
4 touches
1 conflict
0x588380ee…0a5c
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 0x17f5dec852…2f3332
Audit this contract →
← previous block·next block →recent activity