← previous blocknext block →recent activity

Analyzing

Block #106,109,507

18 transactions · 18 stateful · 2026-09-19 06:48:09 UTC

Parallelism

67/100

Blocked

44%

Avg conflicts / tx

1.06

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #106,109,507  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x05cd5432…a826

0x6f6493…b480

12 touches
15 conflicts

0x0de60711…adf2

0x6f6493…b480

12 touches
15 conflicts

0x1b332906…d550

0x6f6493…b480

12 touches
15 conflicts

0x479d888e…33c1

0x6f6493…b480

12 touches
15 conflicts

0x5b6b64cb…af8e

0x6f6493…b480

12 touches
15 conflicts

0x636fb341…c0c0

0x6f6493…b480

12 touches
15 conflicts

0x63c338c5…24d1

0x6f6493…b480

12 touches
15 conflicts

0x7ac517b6…a787

0x6f6493…b480

12 touches
15 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

15 conflicts on slot 0x05cd543217…17a826

← previous block·next block →recent activity