← previous blocknext block →recent activity

Analyzing

Block #101,308,427

21 transactions · 20 stateful · 2026-09-02 10:48:16 UTC

Parallelism

86/100

Blocked

35%

Avg conflicts / tx

0.48

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #101,308,427  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x524f0872…0d12

0x34b655…2a6f

6 touches
3 conflicts

0x5ddc4a77…765e

0x34b655…2a6f

6 touches
3 conflicts

0xb1616a9a…7888

0x851145…3f07

4 touches
1 conflict

0xf362e8a6…6ce6

0x851145…3f07

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x8a7af3fd…72a6

0x34b655…2a6f

4 touches
1 conflict

0x9b69ed2c…03bb

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 0x524f087203…e70d12

← previous block·next block →recent activity