← previous blocknext block →recent activity

Analyzing

Block #101,972,046

13 transactions · 13 stateful · 2026-09-04 18:30:05 UTC

Parallelism

77/100

Blocked

31%

Avg conflicts / tx

0.46

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #101,972,046  ·  13 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

0x045532dd…4b7d

0x34b655…2a6f

6 touches
3 conflicts

0x9bff3222…a246

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xcdcc920e…c0dc

0x34b655…2a6f

4 touches
1 conflict

0xc7bb912f…ad41

0x34b655…2a6f

4 touches
1 conflict

0x9c088939…ddd7

0x34b655…2a6f

4 touches
1 conflict

0xeb1b66a1…ce4e

0x34b655…2a6f

4 touches
1 conflict

0x3fb3f2e2…fef3

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 0x045532dd4b…244b7d

← previous block·next block →recent activity