← previous blocknext block →recent activity

Analyzing

Block #101,673,053

23 transactions · 15 stateful · 2026-09-03 17:22:49 UTC

Parallelism

74/100

Blocked

47%

Avg conflicts / tx

0.57

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #101,673,053  ·  23 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

0x0e903356…3d5b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x8875810e…39f1

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x38e54a9f…52ce

0x34b655…2a6f

4 touches
1 conflict

0x110a3804…f842

0x34b655…2a6f

4 touches
1 conflict

0x742436a7…c4d4

0x34b655…2a6f

4 touches
1 conflict

0x885efce3…7496

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 0x0e90335635…463d5b

← previous block·next block →recent activity