← previous blocknext block →recent activity
Analyzing
Block #96,700,345
17 transactions · 16 stateful · 2026-08-17 06:07:33 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,700,345 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w05w16w07w08w112w213w314w015w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xacd1b162…bee6
0x34b655…2a6f
8 touches
6 conflicts
0xbcbb6bba…1c92
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6026af06…8416
0x34b655…2a6f
6 touches
3 conflicts
0x48532ab5…d4c1
0x34b655…2a6f
4 touches
1 conflict
0x48532ab5…d4c2
0x34b655…2a6f
4 touches
1 conflict
0x714da06b…bfa0
0x34b655…2a6f
4 touches
1 conflict
0xa7234825…2716
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
6 conflicts on slot 0xacd1b16256…3bbee6
Audit this contract →
← previous block·next block →recent activity