← previous blocknext block →recent activity
Analyzing
Block #98,724,439
17 transactions · 16 stateful · 2026-08-24 09:39:57 UTC
Parallelism
53/100
Blocked
63%
Avg conflicts / tx
1.18
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,724,439 · 17 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
3w04w15w27w08w19w210w311w413w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd2dfd9bc…3eec
0x34b655…2a6f
8 touches
6 conflicts
0x2ef1d89b…196d
0x754704…b603
6 touches
3 conflicts
0x00000000…0036
0x35a73b…6042
6 touches
3 conflicts
0xaf831072…51d5
0x69a5f9…2fef
6 touches
3 conflicts
0xaf831072…51d6
0x69a5f9…2fef
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity