← previous blocknext block →recent activity

Analyzing

Block #106,468,103

22 transactions · 20 stateful · 2026-09-20 12:52:58 UTC

Parallelism

82/100

Blocked

40%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #106,468,103  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x2533fe3f…344d

0x34b655…2a6f

8 touches
6 conflicts

0xd563f3a1…94b1

0x34b655…2a6f

8 touches
6 conflicts

0x159cff26…7665

0x34b655…2a6f

6 touches
3 conflicts

0x4265984a…a7d2

0x34b655…2a6f

6 touches
3 conflicts

0x4118bd12…924a

0x34b655…2a6f

6 touches
3 conflicts

0xfc321f86…4c7f

0x34b655…2a6f

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0x1b25f260…c429

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

6 conflicts on slot 0x2533fe3fdb…c5344d

← previous block·next block →recent activity