← previous blocknext block →recent activity
Analyzing
Block #96,191,399
11 transactions · 10 stateful · 2026-08-15 11:27:28 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,191,399 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6d7ed80…2dd2
0x34b655…2a6f
4 touches
1 conflict
0x511f4d1c…65c9
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x35a9f06c…7689
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x59991669…58c6
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
2 touches
0 conflicts
0x8b37f931…1b3f
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 0xb6d7ed800f…572dd2
Audit this contract →
← previous block·next block →recent activity