← previous blocknext block →recent activity
Analyzing
Block #100,584,598
24 transactions · 22 stateful · 2026-08-30 22:06:12 UTC
Parallelism
75/100
Blocked
32%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,584,598 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w09w110w211w112w313w314w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b4edd58…9623
0x34b655…2a6f
10 touches
10 conflicts
0xd814f518…f5b4
0x34b655…2a6f
10 touches
10 conflicts
0x0ec34d4f…5fa1
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x4786839b…c29a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x809f2ba8…89d3
0x34b655…2a6f
6 touches
3 conflicts
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0x6b4edd5859…d59623
Audit this contract →
← previous block·next block →recent activity