← previous blocknext block →recent activity

Analyzing

Block #106,156,124

19 transactions · 17 stateful · 2026-09-19 10:42:47 UTC

Parallelism

79/100

Blocked

35%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #106,156,124  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x02ab954b…e1cc

0x6f6493…b480

7 touches
6 conflicts

0x047dc3b4…024d

0x6f6493…b480

7 touches
6 conflicts

0x08fa0f5b…4d0a

0x6f6493…b480

7 touches
6 conflicts

0x1779e75d…80fb

0x6f6493…b480

7 touches
6 conflicts

0x2616ed7b…3b4d

0x6f6493…b480

7 touches
6 conflicts

0x32fb990f…d23e

0x6f6493…b480

7 touches
6 conflicts

0x3b5940d3…539e

0x6f6493…b480

7 touches
6 conflicts

0x446b7c24…ba69

0x6f6493…b480

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: 0x6f6493e3…08b480

6 conflicts on slot 0x02ab954bd8…54e1cc

← previous block·next block →recent activity