← previous blocknext block →recent activity

Analyzing

Block #106,915,803

20 transactions · 20 stateful · 2026-09-22 02:27:17 UTC

Parallelism

65/100

Blocked

45%

Avg conflicts / tx

1.25

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #106,915,803  ·  20 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

0x85bfd0af…ce96

0x34b655…2a6f

14 touches
21 conflicts

0x08e2f7cd…82ab

0x34b655…2a6f

12 touches
15 conflicts

0x49890ced…6f23

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xfaa764bd…da00

0x34b655…2a6f

4 touches
1 conflict

0x51fc8795…126f

0x34b655…2a6f

4 touches
1 conflict

0x1c01e347…0cc7

0x34b655…2a6f

4 touches
1 conflict

0x7dd96c96…7335

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 0x85bfd0afba…f5ce96

← previous block·next block →recent activity