← previous blocknext block →recent activity
Analyzing
Block #100,792,021
30 transactions · 25 stateful · 2026-08-31 15:29:48 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
1.17
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,792,021 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w07w18w012w113w214w315w417w519w123w125w626w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac389ba9…8b45
0x34b655…2a6f
12 touches
15 conflicts
0xcaa1a41d…b844
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x0b0611f7…e63a
0x34b655…2a6f
6 touches
3 conflicts
0xf279b789…d3c3
0x34b655…2a6f
6 touches
3 conflicts
0xfaf89f45…ced6
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 0xac389ba9d1…e18b45
Audit this contract →
← previous block·next block →recent activity