← previous blocknext block →recent activity

Analyzing

Block #106,186,056

23 transactions · 20 stateful · 2026-09-19 13:13:24 UTC

Parallelism

70/100

Blocked

40%

Avg conflicts / tx

0.83

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #106,186,056  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x2cd2af6f…b80f

0x34b655…2a6f

12 touches
15 conflicts

0xbeedaa05…9eda

0x34b655…2a6f

10 touches
10 conflicts

0x05e1eba1…6491

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x1d351a9b…f2dd

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x932a9590…0b19

0x34b655…2a6f

4 touches
1 conflict

0x976029c0…a4de

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

15 conflicts on slot 0x2cd2af6f33…81b80f

← previous block·next block →recent activity