← previous blocknext block →recent activity
Analyzing
Block #96,824,987
6 transactions · 6 stateful · 2026-08-17 16:34:28 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,824,987 · 6 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xc2eb7778…14e2
0x34b655…2a6f
3 touches
1 conflict
0x30c5329c…711c
0x34b655…2a6f
2 touches
0 conflicts
0x3c0e49c9…7833
0x34b655…2a6f
2 touches
0 conflicts
0x48e6051f…5350
0x34b655…2a6f
2 touches
0 conflicts
0x4f1ad4b4…e00a
0x34b655…2a6f
2 touches
0 conflicts
0x5c16527f…628c
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 0xafd867b7ed…d92b2e
Audit this contract →
← previous block·next block →recent activity