← previous blocknext block →recent activity

Analyzing

Block #106,039,472

18 transactions · 18 stateful · 2026-09-19 00:55:43 UTC

Parallelism

72/100

Blocked

44%

Avg conflicts / tx

0.89

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #106,039,472  ·  18 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

0x01d74708…2aa1

0x6f6493…b480

10 touches
10 conflicts

0x062c5414…f293

0x6f6493…b480

10 touches
10 conflicts

0x0eee3b83…f2e1

0x6f6493…b480

10 touches
10 conflicts

0x1a1dbc2b…1646

0x6f6493…b480

10 touches
10 conflicts

0x26b06c3b…4e2a

0x6f6493…b480

10 touches
10 conflicts

0x288c22de…5ac7

0x6f6493…b480

10 touches
10 conflicts

0x2f2f420d…816d

0x6f6493…b480

10 touches
10 conflicts

0x3055eda7…5423

0x6f6493…b480

10 touches
10 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

10 conflicts on slot 0x01d74708f8…4a2aa1

← previous block·next block →recent activity