← previous blocknext block →recent activity

Analyzing

Block #106,188,556

25 transactions · 22 stateful · 2026-09-19 13:25:59 UTC

Parallelism

52/100

Blocked

50%

Avg conflicts / tx

2.4

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #106,188,556  ·  25 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0x837fb53e…b580

0x34b655…2a6f

20 touches
45 conflicts

0xc824469a…6425

0x34b655…2a6f

18 touches
36 conflicts

0xd62f3741…b903

0x34b655…2a6f

14 touches
21 conflicts

0x159cff26…7665

0x34b655…2a6f

10 touches
10 conflicts

0xcd5c0ecb…4b5f

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x581b829b…9578

0x34b655…2a6f

8 touches
6 conflicts

0x1b25f260…c429

0x34b655…2a6f

6 touches
3 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: Perpl

45 conflicts on slot 0x837fb53e80…d2b580

← previous block·next block →recent activity