← previous blocknext block →recent activity
Analyzing
Block #98,576,122
13 transactions · 12 stateful · 2026-08-23 20:52:27 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,576,122 · 13 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
6w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec48840b…9ddc
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x10f0a1bf…12c3
0x34b655…2a6f
2 touches
0 conflicts
0x2d8c9ff9…8b1d
0x34b655…2a6f
2 touches
0 conflicts
0x3347cbe5…846c
0x34b655…2a6f
2 touches
0 conflicts
0x47e2a668…be99
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 0xec48840b03…c89ddc
Audit this contract →
← previous block·next block →recent activity