← previous blocknext block →recent activity

Analyzing

Block #106,944,723

20 transactions · 19 stateful · 2026-09-22 04:52:50 UTC

Parallelism

70/100

Blocked

42%

Avg conflicts / tx

0.85

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #106,944,723  ·  20 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

0x1556ed58…0d33

0x34b655…2a6f

10 touches
10 conflicts

0x23769ebc…c8ed

0x34b655…2a6f

8 touches
6 conflicts

0x49b9fdd5…9c16

0x34b655…2a6f

8 touches
6 conflicts

0x4cb4372c…155e

0x34b655…2a6f

6 touches
3 conflicts

0x6605505c…6100

0x34b655…2a6f

6 touches
3 conflicts

0xd125c3f8…99aa

0x34b655…2a6f

6 touches
3 conflicts

0x6c60fbcf…8744

0x34b655…2a6f

6 touches
3 conflicts

0xb8dc136f…fb16

0xc8689a…ee79

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 0x1556ed5826…150d33

← previous block·next block →recent activity