← previous blocknext block →recent activity

Analyzing

Block #109,237,347

22 transactions · 19 stateful · 2026-09-30 05:21:59 UTC

Parallelism

77/100

Blocked

42%

Avg conflicts / tx

0.73

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #109,237,347  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0x898d9b8a…d1ef

0x34b655…2a6f

6 touches
3 conflicts

0x9375a764…dca1

0x34b655…2a6f

6 touches
3 conflicts

0xdd276023…d371

0x34b655…2a6f

6 touches
3 conflicts

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0x7f5b2c1d…0e7f

0x34b655…2a6f

4 touches
1 conflict

0x8e99ff06…9eb5

0x34b655…2a6f

4 touches
1 conflict

0x9ebe7d3c…c8b6

0x34b655…2a6f

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

10 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity