← previous blocknext block →recent activity

Analyzing

Block #105,841,564

18 transactions · 16 stateful · 2026-09-18 08:18:28 UTC

Parallelism

89/100

Blocked

31%

Avg conflicts / tx

0.28

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #105,841,564  ·  18 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x359866c7…de7b

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xf5dc501b…8313

0x34b655…2a6f

4 touches
1 conflict

0x3a663e9a…a9c5

0x6571f8…2f53

4 touches
1 conflict

0xd64c8e10…cd25

0x6571f8…2f53

4 touches
1 conflict

0xe1c4d8e8…ffa8

0x6571f8…2f53

4 touches
1 conflict

0xd17580f9…ece1

0x754704…b603

4 touches
1 conflict

0x918415c4…e9d1

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0x359866c739…efde7b

← previous block·next block →recent activity