← previous blocknext block →recent activity
Analyzing
Block #97,656,561
47 transactions · 41 stateful · 2026-08-20 15:10:15 UTC
Parallelism
66/100
Blocked
71%
Avg conflicts / tx
2.72
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #97,656,561 · 47 txs across 16 waves · depth 16
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
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w08w19w010w011w112w113w214w215w317w418w419w522w325w528w429w532w640w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xec7d120d…7084
0x34b655…2a6f
14 touches
21 conflicts
0x9db05bb3…b403
0x065c9d…c394
12 touches
15 conflicts
0x11258774…9892
0x2a68ba…90c5
12 touches
15 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
12 touches
15 conflicts
0xb99b689d…9ff1
0x34b655…2a6f
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0x47b2d2eb…8aa5
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity