← previous blocknext block →recent activity
Analyzing
Block #100,140,049
26 transactions · 21 stateful · 2026-08-29 08:45:35 UTC
Parallelism
73/100
Blocked
52%
Avg conflicts / tx
0.92
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,140,049 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w18w29w110w215w316w418w523w624w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcdd58ff…0711
0x34b655…2a6f
10 touches
10 conflicts
0x9a2d2edc…f7f8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x1a2055c7…9054
0x34b655…2a6f
8 touches
6 conflicts
0x6971813e…8488
0x34b655…2a6f
7 touches
6 conflicts
0x640c4fb2…044a
0x34b655…2a6f
7 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: Perpl
10 conflicts on slot 0xbcdd58ff98…970711
Audit this contract →
← previous block·next block →recent activity