← previous blocknext block →recent activity
Analyzing
Block #98,285,538
24 transactions · 21 stateful · 2026-08-22 20:15:32 UTC
Parallelism
79/100
Blocked
43%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,285,538 · 24 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
1w03w06w07w08w111w113w214w315w016w117w218w321w423w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xaf831072…51d6
0x69a5f9…2fef
8 touches
6 conflicts
0xaf831072…51dc
0x69a5f9…2fef
8 touches
6 conflicts
0x2ef1d89b…196d
0x754704…b603
8 touches
6 conflicts
0x00000000…0036
0x35a73b…6042
8 touches
6 conflicts
0xaf831072…51d5
0x69a5f9…2fef
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity