← previous blocknext block →recent activity

Analyzing

Block #100,154,749

18 transactions · 17 stateful · 2026-08-29 09:59:35 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.39

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,154,749  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x1393d3ba…79d7

0x8964d7…10f8

6 touches
3 conflicts

0x2a07e64e…fe77

0x754704…b603

6 touches
3 conflicts

0x1393d3ba…79d5

0x8964d7…10f8

6 touches
3 conflicts

0x1393d3ba…79d4

0x8964d7…10f8

6 touches
3 conflicts

0x00000000…0008

0x8964d7…10f8

6 touches
3 conflicts

0x1393d3ba…79d0

0x8964d7…10f8

6 touches
3 conflicts

0x1393d3ba…79d1

0x8964d7…10f8

6 touches
3 conflicts

0x9210fb29…265f

0x8964d7…10f8

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: 0x8964d7c9…5b10f8

3 conflicts on slot 0x1393d3bae9…c279d7

← previous block·next block →recent activity