← previous blocknext block →recent activity
Analyzing
Block #100,851,885
24 transactions · 22 stateful · 2026-08-31 20:31:10 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,851,885 · 24 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
5w07w110w011w112w013w114w221w322w023w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec4cdda2…9223
0x40c49f…2af0
7 touches
6 conflicts
0x6518075e…2b17
0x2a68ba…90c5
6 touches
3 conflicts
0x2b54cadb…4425
0xd18b7e…414b
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x5b37bb6b…ab00
0x34b655…2a6f
4 touches
1 conflict
0x5c3953d6…4dcb
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xb37dfb6b…268f
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: 0x40c49f17…d22af0
6 conflicts on slot 0xec4cdda2cc…339223
Audit this contract →
← previous block·next block →recent activity