← previous blocknext block →recent activity
Analyzing
Block #97,827,985
24 transactions · 23 stateful · 2026-08-21 05:39:36 UTC
Parallelism
75/100
Blocked
52%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,827,985 · 24 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
1w02w13w04w15w16w17w28w39w410w511w014w216w117w218w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00096307…5a3d
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x8ebbacca…fad3
0xd32edf…ff58
5 touches
3 conflicts
0x84611dd3…b348
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x93aff45d…1722
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 0x00096307b5…9c5a3d
Audit this contract →
← previous block·next block →recent activity