← previous blocknext block →recent activity
Analyzing
Block #99,978,341
28 transactions · 24 stateful · 2026-08-28 19:11:17 UTC
Parallelism
68/100
Blocked
54%
Avg conflicts / tx
1.25
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #99,978,341 · 28 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w18w210w011w112w013w114w215w316w418w520w627w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61571888…b392
0x34b655…2a6f
14 touches
21 conflicts
0x9d1d78dc…55b9
0x34b655…2a6f
10 touches
10 conflicts
0x2d3930d3…c9b8
0x34b655…2a6f
8 touches
6 conflicts
0xf788c790…e66f
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xd07dc434…c644
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x326a02b5…8dad
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 0x6157188898…efb392
Audit this contract →
← previous block·next block →recent activity