← previous blocknext block →recent activity
Analyzing
Block #97,666,335
12 transactions · 11 stateful · 2026-08-20 16:00:56 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,666,335 · 12 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
1w04w15w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xabf57eb6…416d
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xcfb73083…5138
0x34b655…2a6f
4 touches
1 conflict
0x51dc2b7a…6027
0xd32edf…ff58
3 touches
1 conflict
0x09beabbc…065d
0x188d58…ea8e
2 touches
0 conflicts
0x46cb45de…a566
0x188d58…ea8e
2 touches
0 conflicts
0x01a33778…c2d4
0x34b655…2a6f
2 touches
0 conflicts
0x280d1119…ee4d
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 0xabf57eb66c…0a416d
Audit this contract →
← previous block·next block →recent activity