← previous blocknext block →recent activity

Analyzing

Block #108,923,275

19 transactions · 18 stateful · 2026-09-29 02:57:36 UTC

Parallelism

84/100

Blocked

28%

Avg conflicts / tx

0.32

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #108,923,275  ·  19 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

0xf79df061…e005

0xe52b14…7230

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x443a3e47…f4a4

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002d

0x1b6862…e19c

4 touches
1 conflict

0x6235638c…643b

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb85

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: 0xe52b1424…bb7230

1 conflict on slot 0xf79df061c7…91e005

← previous block·next block →recent activity