← previous blocknext block →recent activity

Analyzing

Block #106,934,022

16 transactions · 16 stateful · 2026-09-22 03:58:58 UTC

Parallelism

56/100

Blocked

56%

Avg conflicts / tx

1.56

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #106,934,022  ·  16 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

0xe720a4c6…8eb0

0x34b655…2a6f

14 touches
21 conflicts

0x3780a34a…b50a

0x34b655…2a6f

14 touches
21 conflicts

0xba1edffb…323e

0x34b655…2a6f

14 touches
21 conflicts

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xae76fcd2…d26a

0x34b655…2a6f

4 touches
1 conflict

0xb50ef533…79e4

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

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

21 conflicts on slot 0xe720a4c698…508eb0

← previous block·next block →recent activity