← previous blocknext block →recent activity
Analyzing
Block #97,363,774
25 transactions · 22 stateful · 2026-08-19 14:06:17 UTC
Parallelism
68/100
Blocked
55%
Avg conflicts / tx
1.32
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #97,363,774 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w27w38w49w210w311w412w515w516w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x917f99a5…7989
0x34b655…2a6f
14 touches
21 conflicts
0xec7d120d…7084
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x0c280953…1798
0x34b655…2a6f
6 touches
3 conflicts
0x612a8656…e330
0x34b655…2a6f
6 touches
3 conflicts
0x0d44c3fe…932a
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
21 conflicts on slot 0x917f99a53e…3d7989
Audit this contract →
← previous block·next block →recent activity