← previous blocknext block →recent activity
Analyzing
Block #98,322,751
23 transactions · 22 stateful · 2026-08-22 23:22:49 UTC
Parallelism
70/100
Blocked
32%
Avg conflicts / tx
0.57
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,322,751 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w08w110w111w212w320w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xcd6e6faa…f569
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x3c78ca04…432c
0x34b655…2a6f
4 touches
1 conflict
0x4f508b5b…7790
0x34b655…2a6f
4 touches
1 conflict
0x8354123e…3cea
0x34b655…2a6f
4 touches
1 conflict
0x85ee2c46…3b0f
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
3 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity