← previous blocknext block →recent activity
Analyzing
Block #100,726,140
28 transactions · 22 stateful · 2026-08-31 09:58:13 UTC
Parallelism
86/100
Blocked
45%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,726,140 · 28 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
1w02w03w04w18w19w212w013w114w115w220w322w023w124w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x53e50026…6d8c
0x34ae4d…3fc5
4 touches
1 conflict
0x6eff310a…c34c
0x34ae4d…3fc5
4 touches
1 conflict
0x7f4a8466…f2cc
0x34ae4d…3fc5
4 touches
1 conflict
0xe49b1b9b…0be1
0x34ae4d…3fc5
4 touches
1 conflict
0x54c6fb44…369a
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity