← previous blocknext block →recent activity
Analyzing
Block #100,032,955
26 transactions · 25 stateful · 2026-08-28 23:46:17 UTC
Parallelism
88/100
Blocked
16%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,032,955 · 26 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w112w013w114w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68e4bc91…ad89
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0ed7cc0b…ee52
0x34b655…2a6f
4 touches
1 conflict
0x07bb3f5a…617e
0x34b655…2a6f
4 touches
1 conflict
0x4ec9ff52…e6f7
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
3 conflicts on slot 0x68e4bc91a6…35ad89
Audit this contract →
← previous block·next block →recent activity