← previous blocknext block →recent activity
Analyzing
Block #96,255,593
15 transactions · 11 stateful · 2026-08-15 16:50:21 UTC
Parallelism
87/100
Blocked
9%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,255,593 · 15 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
5w06w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf6de35e…bafd
0x34b655…2a6f
4 touches
1 conflict
0x39bd1fab…a39c
0x34b655…2a6f
4 touches
1 conflict
0x0be747d5…22e0
0x34b655…2a6f
4 touches
1 conflict
0x5ff5ddb4…252a
0x34b655…2a6f
4 touches
1 conflict
0x0be747d5…22e1
0x34b655…2a6f
4 touches
1 conflict
0xa5a8ffca…8de2
0x34b655…2a6f
4 touches
1 conflict
0x2ffa0115…ed47
0x34b655…2a6f
2 touches
0 conflicts
0x4a5956ef…e226
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 0xbf6de35e01…bfbafd
Audit this contract →
← previous block·next block →recent activity