← previous blocknext block →recent activity
Analyzing
Block #100,143,211
21 transactions · 17 stateful · 2026-08-29 09:01:30 UTC
Parallelism
86/100
Blocked
24%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,143,211 · 21 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
2w03w04w06w18w013w114w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ce1b956…48c9
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfc8cd993…5c11
0x34b655…2a6f
4 touches
1 conflict
0x15698ac9…2a46
0x34b655…2a6f
4 touches
1 conflict
0x6f232437…749d
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab0
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
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 0x1ce1b956c5…6b48c9
Audit this contract →
← previous block·next block →recent activity