← previous blocknext block →recent activity
Analyzing
Block #98,504,561
17 transactions · 17 stateful · 2026-08-23 14:38:54 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.82
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,504,561 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w08w09w210w111w212w313w114w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x334209f4…aace
0x34b655…2a6f
6 touches
3 conflicts
0x5e2ea201…12de
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5cd36012…d899
0x34b655…2a6f
4 touches
1 conflict
0x5cd36012…d89a
0x34b655…2a6f
4 touches
1 conflict
0xbb1747e2…f78b
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 0x334209f432…7caace
Audit this contract →
← previous block·next block →recent activity