← previous blocknext block →recent activity
Analyzing
Block #96,544,078
10 transactions · 10 stateful · 2026-08-16 17:01:36 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,544,078 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x17f5dec8…3332
0x34b655…2a6f
4 touches
1 conflict
0x8d175439…fb79
0x34b655…2a6f
4 touches
1 conflict
0x9937c4f0…1cc4
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x48717abe…be13
0x34b655…2a6f
2 touches
0 conflicts
0x5aed1bd2…7afa
0x34b655…2a6f
2 touches
0 conflicts
0x63616bcd…f87f
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity