← previous blocknext block →recent activity
Analyzing
Block #100,135,765
16 transactions · 16 stateful · 2026-08-29 08:23:56 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,135,765 · 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
1w06w18w09w110w211w313w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6828f2a6…0cf8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xfb14d7f1…e509
0x34b655…2a6f
4 touches
1 conflict
0x1e168c8b…6945
0x34b655…2a6f
4 touches
1 conflict
0x4ec9ff52…e6f7
0x34b655…2a6f
4 touches
1 conflict
0x50c61506…343f
0x34b655…2a6f
4 touches
1 conflict
0x72083f0d…082a
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x6828f2a6ec…970cf8
Audit this contract →
← previous block·next block →recent activity