← previous blocknext block →recent activity
Analyzing
Block #100,749,156
27 transactions · 21 stateful · 2026-08-31 11:53:59 UTC
Parallelism
70/100
Blocked
52%
Avg conflicts / tx
1.11
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,749,156 · 27 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w08w19w110w212w318w019w421w522w623w124w126w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55192654…91fe
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x875fe21d…2e63
0x34b655…2a6f
8 touches
6 conflicts
0x14174d82…41d3
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x4d42f16e…a6c7
0x1b6862…e19c
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
15 conflicts on slot 0x551926541c…2e91fe
Audit this contract →
← previous block·next block →recent activity