← previous blocknext block →recent activity
Analyzing
Block #98,658,313
17 transactions · 17 stateful · 2026-08-24 04:00:24 UTC
Parallelism
76/100
Blocked
53%
Avg conflicts / tx
0.88
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,658,313 · 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
2w03w14w05w16w27w09w010w111w212w313w114w316w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xb7b16dd0…0426
0x34b655…2a6f
6 touches
3 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
4 touches
1 conflict
0x6ae20d96…12fa
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity