← previous blocknext block →recent activity
Analyzing
Block #97,666,116
25 transactions · 24 stateful · 2026-08-20 15:59:46 UTC
Parallelism
76/100
Blocked
42%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,666,116 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w09w110w211w312w413w114w415w519w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02b4abec…397d
0x34b655…2a6f
8 touches
6 conflicts
0x5c45ce93…9285
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd336496d…f4b9
0x34b655…2a6f
6 touches
3 conflicts
0xad78e96e…a868
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x22e0cc1d…ad0d
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
6 conflicts on slot 0x02b4abec82…9b397d
Audit this contract →
← previous block·next block →recent activity