← previous blocknext block →recent activity

Analyzing

Block #106,958,522

18 transactions · 18 stateful · 2026-09-22 06:02:18 UTC

Parallelism

61/100

Blocked

50%

Avg conflicts / tx

1.11

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #106,958,522  ·  18 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

0xca841faa…486a

0x34b655…2a6f

12 touches
15 conflicts

0x3243e72f…1f6d

0x34b655…2a6f

4 touches
1 conflict

0x51aa664e…d3b8

0x34b655…2a6f

4 touches
1 conflict

0x5969523e…5191

0x34b655…2a6f

4 touches
1 conflict

0x6d5d1fb5…86a7

0x34b655…2a6f

4 touches
1 conflict

0xa140ac77…1f0c

0x34b655…2a6f

4 touches
1 conflict

0xa7d3cb90…e1d9

0x34b655…2a6f

4 touches
1 conflict

0xabfdfd0e…20bf

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 0xca841faae5…71486a

← previous block·next block →recent activity