← previous blocknext block →recent activity

Analyzing

Block #106,373,382

20 transactions · 18 stateful · 2026-09-20 04:56:13 UTC

Parallelism

75/100

Blocked

39%

Avg conflicts / tx

0.9

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #106,373,382  ·  20 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

0x2dce2df2…0c51

0x34b655…2a6f

10 touches
10 conflicts

0xac0b4a08…faae

0x34b655…2a6f

6 touches
3 conflicts

0x3fa1fac4…826c

0x34b655…2a6f

6 touches
3 conflicts

0x0262e1c6…52e1

0x34b655…2a6f

6 touches
3 conflicts

0x2029b74e…c206

0x34b655…2a6f

6 touches
3 conflicts

0x80398c66…f3cc

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x786d66ce…ae70

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

10 conflicts on slot 0x2dce2df2b2…5a0c51

← previous block·next block →recent activity