← previous blocknext block →recent activity
Analyzing
Block #97,565,963
53 transactions · 47 stateful · 2026-08-20 07:28:30 UTC
Parallelism
72/100
Blocked
62%
Avg conflicts / tx
2.17
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #97,565,963 · 53 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w07w18w010w111w214w015w119w228w331w133w236w341w442w543w644w746w947w1048w1149w1250w1351w1452w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d10975…0d07
0x34b655…2a6f
24 touches
66 conflicts
0xea02471d…1542
0x34b655…2a6f
24 touches
66 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
20 touches
45 conflicts
0x94dabb65…43a3
0x34b655…2a6f
18 touches
36 conflicts
0xc12b04b0…884b
0x34b655…2a6f
9 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x5e7da795…a150
0x34b655…2a6f
8 touches
6 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
66 conflicts on slot 0xf3d10975b0…050d07
Audit this contract →
← previous block·next block →recent activity