← previous blocknext block →recent activity
Analyzing
Block #98,739,405
12 transactions · 11 stateful · 2026-08-24 10:55:14 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,739,405 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc844ab5…4c6d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x9d73409a…a383
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x0691eca1…0d6a
0x34b655…2a6f
2 touches
0 conflicts
0x45932996…b214
0x34b655…2a6f
2 touches
0 conflicts
0x49ecf9bd…88b9
0x34b655…2a6f
2 touches
0 conflicts
0x55f5a89c…5e40
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xcc844ab542…814c6d
Audit this contract →
← previous block·next block →recent activity