← previous blocknext block →recent activity
Analyzing
Block #98,424,896
20 transactions · 20 stateful · 2026-08-23 07:56:42 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.25
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,424,896 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w07w110w111w212w213w314w415w518w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x79e8f935…c3b6
0x34b655…2a6f
10 touches
10 conflicts
0x9cf9008a…d826
0x34b655…2a6f
8 touches
6 conflicts
0x2244cd52…ab65
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0x640c4fb2…044a
0x34b655…2a6f
7 touches
6 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
15 conflicts on slot 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity