← previous blocknext block →recent activity
Analyzing
Block #96,611,824
17 transactions · 14 stateful · 2026-08-16 22:42:20 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,611,824 · 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
7w08w19w110w211w214w315w416w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff4a358a…762f
0x34b655…2a6f
4 touches
1 conflict
0x3104f796…8ea3
0x34b655…2a6f
4 touches
1 conflict
0x33b4c2ba…961a
0x34b655…2a6f
4 touches
1 conflict
0x4c214bb3…c5d3
0x34b655…2a6f
4 touches
1 conflict
0x5f447bf3…57c7
0x34b655…2a6f
4 touches
1 conflict
0x665a9bd1…6c3b
0x34b655…2a6f
4 touches
1 conflict
0x840d3ab7…c8c4
0x34b655…2a6f
4 touches
1 conflict
0x86c98782…f3b7
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 0xff4a358a00…50762f
Audit this contract →
← previous block·next block →recent activity