← previous blocknext block →recent activity
Analyzing
Block #98,324,220
30 transactions · 25 stateful · 2026-08-22 23:30:13 UTC
Parallelism
63/100
Blocked
56%
Avg conflicts / tx
1.7
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #98,324,220 · 30 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w19w110w211w212w313w418w521w624w727w829w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xb7b16dd0…0426
0x34b655…2a6f
12 touches
15 conflicts
0x177e3941…97ae
0x34b655…2a6f
6 touches
3 conflicts
0x3e59474b…04b2
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0547420b…fc46
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
36 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity