← previous blocknext block →recent activity

Analyzing

Block #105,673,009

22 transactions · 19 stateful · 2026-09-17 18:08:52 UTC

Parallelism

73/100

Blocked

42%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #105,673,009  ·  22 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

0x0ddcc529…6d32

0x6f6493…b480

12 touches
15 conflicts

0x1662a729…3dd5

0x6f6493…b480

12 touches
15 conflicts

0x28e83964…e3d7

0x6f6493…b480

12 touches
15 conflicts

0x2ddc7d3b…5842

0x6f6493…b480

12 touches
15 conflicts

0x2f50f54c…69f9

0x6f6493…b480

12 touches
15 conflicts

0x303f1ea7…331b

0x6f6493…b480

12 touches
15 conflicts

0x32fc3f23…e12e

0x6f6493…b480

12 touches
15 conflicts

0x4bb83609…00b7

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 0x0ddcc529f6…896d32

← previous block·next block →recent activity