← previous blocknext block →recent activity
Analyzing
Block #97,841,255
20 transactions · 19 stateful · 2026-08-21 06:46:46 UTC
Parallelism
85/100
Blocked
37%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,841,255 · 20 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
2w04w15w06w17w08w110w011w012w115w216w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x6434c774…f635
0x34b655…2a6f
4 touches
1 conflict
0xb9868b52…c77f
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 0x7de579746e…f0f5ba
Audit this contract →
← previous block·next block →recent activity