← previous blocknext block →recent activity

Analyzing

Block #105,930,501

23 transactions · 21 stateful · 2026-09-18 15:47:07 UTC

Parallelism

74/100

Blocked

33%

Avg conflicts / tx

0.61

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #105,930,501  ·  23 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

0xb9e03d71…72da

0x34b655…2a6f

10 touches
10 conflicts

0x17d87f0d…bfc5

0x34b655…2a6f

8 touches
6 conflicts

0xe283e878…7262

0x34b655…2a6f

8 touches
6 conflicts

0x49890ced…6f23

0x34b655…2a6f

6 touches
3 conflicts

0x4c8d4ff7…aa51

0x34b655…2a6f

6 touches
3 conflicts

0xec7d120d…7084

0x34b655…2a6f

4 touches
1 conflict

0x4073f47e…39e6

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

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

10 conflicts on slot 0xb9e03d7117…1672da

← previous block·next block →recent activity