← previous blocknext block →recent activity
Analyzing
Block #100,585,964
21 transactions · 17 stateful · 2026-08-30 22:13:05 UTC
Parallelism
62/100
Blocked
41%
Avg conflicts / tx
0.95
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,585,964 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w011w112w213w314w415w516w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3baa205…f26e
0x34b655…2a6f
12 touches
15 conflicts
0x792b69bf…9c47
0x34b655…2a6f
12 touches
15 conflicts
0xc0e4fec9…aec9
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd895ee0b…d301
0x34b655…2a6f
6 touches
3 conflicts
0xf51ec09c…b4a9
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 0xc3baa205b9…b3f26e
Audit this contract →
← previous block·next block →recent activity