← previous blocknext block →recent activity
Analyzing
Block #97,731,924
25 transactions · 21 stateful · 2026-08-20 21:34:48 UTC
Parallelism
68/100
Blocked
52%
Avg conflicts / tx
1.08
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #97,731,924 · 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
4w05w06w19w210w311w412w516w117w218w221w622w724w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc56bb09e…9c88
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x48061971…8878
0x34b655…2a6f
4 touches
1 conflict
0x6a34f692…092b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
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
21 conflicts on slot 0xc56bb09e4e…b79c88
Audit this contract →
← previous block·next block →recent activity