← previous blocknext block →recent activity
Analyzing
Block #100,617,127
24 transactions · 23 stateful · 2026-08-31 00:49:51 UTC
Parallelism
79/100
Blocked
52%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,617,127 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w06w19w010w111w212w013w115w216w018w319w320w123w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x132750fd…039b
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xe2de1aea…8024
0x34b655…2a6f
6 touches
3 conflicts
0x5086c64a…28ba
0x34b655…2a6f
4 touches
1 conflict
0x62552a2a…7897
0x34b655…2a6f
4 touches
1 conflict
0xb0f2a64a…656a
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 0x132750fd00…b2039b
Audit this contract →
← previous block·next block →recent activity