← previous blocknext block →recent activity

Analyzing

Block #105,471,119

19 transactions · 19 stateful · 2026-09-17 01:12:42 UTC

Parallelism

68/100

Blocked

42%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #105,471,119  ·  19 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

0x0fa13236…5ced

0x6f6493…b480

12 touches
15 conflicts

0x103fef42…a87b

0x6f6493…b480

12 touches
15 conflicts

0x15021b8d…7e13

0x6f6493…b480

12 touches
15 conflicts

0x25486a13…fd2d

0x6f6493…b480

12 touches
15 conflicts

0x295b9d3b…1509

0x6f6493…b480

12 touches
15 conflicts

0x39e7abce…403b

0x6f6493…b480

12 touches
15 conflicts

0x502e596d…00a6

0x6f6493…b480

12 touches
15 conflicts

0x609a79c9…e4db

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 0x0fa132363a…ae5ced

← previous block·next block →recent activity