← previous blocknext block →recent activity
Analyzing
Block #97,898,204
21 transactions · 19 stateful · 2026-08-21 11:40:28 UTC
Parallelism
81/100
Blocked
32%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,898,204 · 21 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
1w02w13w27w08w19w110w213w014w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb63ef486…0dcc
0x34b655…2a6f
6 touches
3 conflicts
0x63aaf27d…312e
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x058882a5…6588
0x34b655…2a6f
4 touches
1 conflict
0x73e7931b…90d0
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
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 0xb63ef48684…2d0dcc
Audit this contract →
← previous block·next block →recent activity