← previous blocknext block →recent activity

Analyzing

Block #102,215,608

22 transactions · 20 stateful · 2026-09-05 15:04:48 UTC

Parallelism

86/100

Blocked

30%

Avg conflicts / tx

0.41

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,215,608  ·  22 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

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0xffc921ce…dc0d

0x34b655…2a6f

6 touches
3 conflicts

0xd17580f9…ece1

0x754704…b603

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x53103bb4…02a1

0x34b655…2a6f

4 touches
1 conflict

0x56e0d685…c960

0x34b655…2a6f

4 touches
1 conflict

0x6823c28e…594c

0x34b655…2a6f

4 touches
1 conflict

0x79ec4509…1f61

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 0x51fc8795c8…57126f

← previous block·next block →recent activity