← previous blocknext block →recent activity
Analyzing
Block #100,789,214
40 transactions · 37 stateful · 2026-08-31 15:15:39 UTC
Parallelism
85/100
Blocked
57%
Avg conflicts / tx
1.27
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,789,214 · 40 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w08w09w110w011w012w113w314w116w125w227w428w529w230w131w232w233w337w339w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11b69a7e…334e
0x01bff4…1071
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
8 touches
6 conflicts
0xa952c504…7b64
0x34b655…2a6f
8 touches
6 conflicts
0x265e09d5…c3ce
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0x37699b20…1071
0x1b6862…e19c
6 touches
3 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: 0x01bff417…bc1071
15 conflicts on slot 0x11b69a7ea1…83334e
Audit this contract →
← previous block·next block →recent activity