← previous blocknext block →recent activity
Analyzing
Block #100,031,763
16 transactions · 16 stateful · 2026-08-28 23:40:16 UTC
Parallelism
75/100
Blocked
19%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,031,763 · 16 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
1w09w111w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x974e6bfb…8a22
0x34b655…2a6f
6 touches
3 conflicts
0x61571888…b392
0x34b655…2a6f
6 touches
3 conflicts
0xf1218340…df46
0x34b655…2a6f
4 touches
1 conflict
0x4fce3905…6f4f
0x34b655…2a6f
4 touches
1 conflict
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity