← previous blocknext block →recent activity

Analyzing

Block #101,937,210

17 transactions · 17 stateful · 2026-09-04 15:33:28 UTC

Parallelism

65/100

Blocked

53%

Avg conflicts / tx

1.06

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #101,937,210  ·  17 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

0xe542bb66…a4db

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xe124586e…e7b3

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

4 touches
1 conflict

0x5aca92a2…b218

0x34b655…2a6f

4 touches
1 conflict

0x60a536a6…ef7a

0x34b655…2a6f

4 touches
1 conflict

0x7d25ae0c…4111

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

6 conflicts on slot 0xe542bb66f9…35a4db

← previous block·next block →recent activity