← previous blocknext block →recent activity
Analyzing
Block #100,612,691
26 transactions · 24 stateful · 2026-08-31 00:27:32 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
0.85
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,612,691 · 26 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
3w04w17w29w310w412w513w614w715w216w318w024w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a6c869d…e3b1
0x34b655…2a6f
10 touches
10 conflicts
0xa6d40b7f…2969
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
6 touches
3 conflicts
0x0476d77b…a514
0x34b655…2a6f
6 touches
3 conflicts
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0x6a6c869d30…7ae3b1
Audit this contract →
← previous block·next block →recent activity