← previous blocknext block →recent activity
Analyzing
Block #100,432,933
20 transactions · 19 stateful · 2026-08-30 09:23:08 UTC
Parallelism
85/100
Blocked
26%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,432,933 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w08w09w010w111w012w117w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae51bb0a…6895
0x34b655…2a6f
6 touches
3 conflicts
0x7a84234e…6a18
0x34b655…2a6f
6 touches
3 conflicts
0xf039e2f8…3d8a
0x34b655…2a6f
4 touches
1 conflict
0xd7908b5f…56b9
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x4ec9ff52…e6f7
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 0xae51bb0a66…246895
Audit this contract →
← previous block·next block →recent activity