← previous blocknext block →recent activity

Analyzing

Block #101,934,286

19 transactions · 19 stateful · 2026-09-04 15:18:36 UTC

Parallelism

68/100

Blocked

37%

Avg conflicts / tx

0.89

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #101,934,286  ·  19 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x470b41f6…fc68

0x34b655…2a6f

6 touches
3 conflicts

0x65903ef9…2567

0x34b655…2a6f

6 touches
3 conflicts

0x67043b0b…97d7

0x34b655…2a6f

4 touches
1 conflict

0x6c28863e…840e

0x34b655…2a6f

4 touches
1 conflict

0x6e7eb884…4fab

0x34b655…2a6f

4 touches
1 conflict

0x7e273bc0…5dbc

0x34b655…2a6f

4 touches
1 conflict

0x897879a1…9c78

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity