← previous blocknext block →recent activity
Analyzing
Block #100,229,541
34 transactions · 31 stateful · 2026-08-29 16:16:04 UTC
Parallelism
68/100
Blocked
68%
Avg conflicts / tx
1.41
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #100,229,541 · 34 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w27w08w010w111w213w114w315w317w218w419w520w623w124w225w326w429w130w731w833w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0x065ff70b…356d
0x40c49f…2af0
8 touches
6 conflicts
0x3f81bcfb…2905
0x40c49f…2af0
8 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x70e677f5…e3bd
0x34b655…2a6f
8 touches
6 conflicts
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity