← previous blocknext block →recent activity

Analyzing

Block #101,307,306

22 transactions · 20 stateful · 2026-09-02 10:42:38 UTC

Parallelism

82/100

Blocked

30%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #101,307,306  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xf48fa71e…bb52

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x6b595a5d…894c

0x34b655…2a6f

6 touches
3 conflicts

0xf9874e36…beed

0x34b655…2a6f

4 touches
1 conflict

0x6771eae2…7014

0x34b655…2a6f

4 touches
1 conflict

0xb110a2d1…1c93

0x34b655…2a6f

4 touches
1 conflict

0xbc8fb280…76a3

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

3 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity