← previous blocknext block →recent activity
Analyzing
Block #98,770,363
31 transactions · 27 stateful · 2026-08-24 13:31:06 UTC
Parallelism
84/100
Blocked
26%
Avg conflicts / tx
0.35
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,770,363 · 31 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w08w110w111w212w313w319w428w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x47c131f8…fb66
0x34b655…2a6f
4 touches
1 conflict
0x5f430f62…c362
0x34b655…2a6f
4 touches
1 conflict
0x733c7779…a647
0x34b655…2a6f
4 touches
1 conflict
0x9654e93b…e153
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity