← previous blocknext block →recent activity
Analyzing
Block #97,526,723
36 transactions · 35 stateful · 2026-08-20 04:09:36 UTC
Parallelism
69/100
Blocked
60%
Avg conflicts / tx
1.33
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #97,526,723 · 36 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w05w16w07w18w29w310w411w512w114w419w520w627w235w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x1dc86774…166a
0x34b655…2a6f
8 touches
6 conflicts
0xb371802a…310c
0x34b655…2a6f
7 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xce06a0f7…efef
0x34b655…2a6f
6 touches
3 conflicts
0x35c37635…11a6
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity