← previous blocknext block →recent activity
Analyzing
Block #96,325,128
11 transactions · 9 stateful · 2026-08-15 22:40:05 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,325,128 · 11 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
6w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4db760d…fc5c
0x34b655…2a6f
4 touches
1 conflict
0x1e1f8d85…2092
0x34b655…2a6f
4 touches
1 conflict
0x2029b74e…c206
0x34b655…2a6f
4 touches
1 conflict
0x3f9a1b4b…664e
0x34b655…2a6f
4 touches
1 conflict
0x47da1e40…7158
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xa4f6a0ed…6e25
0x34b655…2a6f
4 touches
1 conflict
0xa4f6a0ed…6e26
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
1 conflict on slot 0xf4db760d0a…f0fc5c
Audit this contract →
← previous block·next block →recent activity