← previous blocknext block →recent activity

Analyzing

Block #106,016,685

27 transactions · 19 stateful · 2026-09-18 23:01:02 UTC

Parallelism

70/100

Blocked

53%

Avg conflicts / tx

1.07

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #106,016,685  ·  27 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

14 touches
21 conflicts

0x085df2c1…305a

0x34b655…2a6f

6 touches
3 conflicts

0xe3698f79…4512

0x34b655…2a6f

6 touches
3 conflicts

0x65903ef9…2567

0x34b655…2a6f

6 touches
3 conflicts

0xfadc118d…5d64

0x34b655…2a6f

6 touches
3 conflicts

0x3f152ba8…cea6

0x34b655…2a6f

4 touches
1 conflict

0x8b76e9f2…54ee

0x34b655…2a6f

4 touches
1 conflict

0x9ae859db…2d84

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

21 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity