← previous blocknext block →recent activity
Analyzing
Block #96,302,417
10 transactions · 9 stateful · 2026-08-15 20:45:51 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,302,417 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w06w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c88208a…cd3a
0x34b655…2a6f
4 touches
1 conflict
0x325da89c…f96b
0x34b655…2a6f
4 touches
1 conflict
0x514e8c17…48c0
0x34b655…2a6f
4 touches
1 conflict
0x0d488000…3831
0x34b655…2a6f
4 touches
1 conflict
0x0edd0861…8bf1
0x34b655…2a6f
2 touches
0 conflicts
0x11db128b…1153
0x34b655…2a6f
2 touches
0 conflicts
0x22f59c1f…c61d
0x34b655…2a6f
2 touches
0 conflicts
0x23253ea8…e0a4
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x5c88208a1e…20cd3a
Audit this contract →
← previous block·next block →recent activity