← previous blocknext block →recent activity
Analyzing
Block #100,611,262
23 transactions · 23 stateful · 2026-08-31 00:20:21 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.91
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,611,262 · 23 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
4w06w17w29w010w111w312w013w414w415w517w521w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7ce83b1…2c96
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x72924751…cdcf
0x34b655…2a6f
6 touches
3 conflicts
0xccebf5c5…8758
0x34b655…2a6f
6 touches
3 conflicts
0x51087f5a…61f7
0x34b655…2a6f
6 touches
3 conflicts
0x890a8231…345d
0x34b655…2a6f
6 touches
3 conflicts
0xee192525…bd26
0x34b655…2a6f
5 touches
3 conflicts
0x6636a104…d595
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
15 conflicts on slot 0xb7ce83b1b6…352c96
Audit this contract →
← previous block·next block →recent activity