← previous blocknext block →recent activity
Analyzing
Block #97,397,076
28 transactions · 27 stateful · 2026-08-19 17:15:21 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,397,076 · 28 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
1w02w04w05w16w07w110w211w312w413w525w426w527w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xd79ebafc…2161
0x34b655…2a6f
6 touches
3 conflicts
0x6bc293e9…556e
0x34b655…2a6f
6 touches
3 conflicts
0xa50f5e4b…d9cb
0x34b655…2a6f
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
15 conflicts on slot 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity