← previous blocknext block →recent activity
Analyzing
Block #96,496,221
13 transactions · 11 stateful · 2026-08-16 13:00:39 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,496,221 · 13 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
5w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae4a282a…f2ea
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x2fbf2475…bbc3
0x34b655…2a6f
2 touches
0 conflicts
0x31519d10…f76b
0x34b655…2a6f
2 touches
0 conflicts
0x36890fff…f3d1
0x34b655…2a6f
2 touches
0 conflicts
0x45321d59…fc8a
0x34b655…2a6f
2 touches
0 conflicts
0x48b58394…2894
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 0xae4a282a40…25f2ea
Audit this contract →
← previous block·next block →recent activity