← previous blocknext block →recent activity
Analyzing
Block #98,504,839
14 transactions · 14 stateful · 2026-08-23 14:40:22 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,504,839 · 14 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
5w06w17w08w110w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bfc672f…4d28
0x34b655…2a6f
6 touches
3 conflicts
0x12ea6b9f…260f
0x34b655…2a6f
6 touches
3 conflicts
0x68d07e44…48dc
0x34b655…2a6f
5 touches
3 conflicts
0x172b0de5…980b
0x34b655…2a6f
4 touches
1 conflict
0xfb14d7f1…e509
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xba9f9225…2ead
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 0x2bfc672ff5…fc4d28
Audit this contract →
← previous block·next block →recent activity