← previous blocknext block →recent activity
Analyzing
Block #100,230,032
26 transactions · 24 stateful · 2026-08-29 16:18:32 UTC
Parallelism
85/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,230,032 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w06w17w29w311w012w113w214w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3aa2022…9e09
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x5311f864…0984
0x754704…b603
6 touches
3 conflicts
0xd1199663…b276
0x928dc8…8207
4 touches
1 conflict
0x0b0611f7…e63a
0x34b655…2a6f
4 touches
1 conflict
0xd1199663…b278
0x928dc8…8207
4 touches
1 conflict
0x29cd05f5…390c
0x34b655…2a6f
4 touches
1 conflict
0xd1199663…b273
0x928dc8…8207
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
6 conflicts on slot 0xb3aa2022cd…dd9e09
Audit this contract →
← previous block·next block →recent activity