← previous blocknext block →recent activity
Analyzing
Block #98,059,518
20 transactions · 20 stateful · 2026-08-22 01:17:41 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,059,518 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w18w09w110w213w214w315w416w517w618w719w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0x326a02b5…8dad
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
10 touches
10 conflicts
0x41be9e75…9773
0x34b655…2a6f
8 touches
6 conflicts
0x84849074…1ca2
0x34b655…2a6f
7 touches
6 conflicts
0xf88ccd07…a684
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
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
21 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity