← previous blocknext block →recent activity
Analyzing
Block #97,911,212
22 transactions · 22 stateful · 2026-08-21 12:46:46 UTC
Parallelism
86/100
Blocked
36%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,911,212 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w06w07w18w210w011w113w016w117w118w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x309f47c0…e1cf
0x34b655…2a6f
6 touches
3 conflicts
0x0d8152a0…f7f4
0x34b655…2a6f
6 touches
3 conflicts
0xe2d50773…c39e
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x3b2dfb32…949b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x261cbea7…e35e
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 0x309f47c03f…49e1cf
Audit this contract →
← previous block·next block →recent activity