← previous blocknext block →recent activity

Analyzing

Block #103,221,153

14 transactions · 14 stateful · 2026-09-09 03:44:42 UTC

Parallelism

86/100

Blocked

21%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #103,221,153  ·  14 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x4de0b2a2…784f

0xc8689a…ee79

4 touches
1 conflict

0x1f00a5b3…bf76

0x34b655…2a6f

4 touches
1 conflict

0x41469894…598f

0x34b655…2a6f

4 touches
1 conflict

0x41469894…5990

0x34b655…2a6f

4 touches
1 conflict

0x5e9fba25…90da

0x34b655…2a6f

4 touches
1 conflict

0x8e5cc690…b06b

0x34b655…2a6f

4 touches
1 conflict

0x9a5d171e…0f70

0x34b655…2a6f

4 touches
1 conflict

0xb349d74b…8627

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: Settlement / Helper

1 conflict on slot 0x4de0b2a2dc…5e784f

← previous block·next block →recent activity