← previous blocknext block →recent activity
Analyzing
Block #97,563,076
27 transactions · 23 stateful · 2026-08-20 07:13:46 UTC
Parallelism
74/100
Blocked
57%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,563,076 · 27 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w07w28w39w010w111w412w525w626w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda1f3e2c…b73d
0x34b655…2a6f
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xeaeb996b…7ab2
0x34b655…2a6f
8 touches
6 conflicts
0x779cc2f3…fde1
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0x2b96aa12…71d8
0x065c9d…c394
6 touches
3 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
10 conflicts on slot 0xda1f3e2ca4…a6b73d
Audit this contract →
← previous block·next block →recent activity