← previous blocknext block →recent activity

Analyzing

Block #102,642,574

16 transactions · 16 stateful · 2026-09-07 03:07:54 UTC

Parallelism

81/100

Blocked

38%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,642,574  ·  16 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

0x072c7ca8…604d

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

4 touches
1 conflict

0x7dd96c96…7335

0x34b655…2a6f

4 touches
1 conflict

0x9a8af3c2…e4ae

0x34b655…2a6f

4 touches
1 conflict

0x9c2fc330…0091

0x34b655…2a6f

4 touches
1 conflict

0xc446711e…b7cb

0x99c7a7…8bf0

4 touches
1 conflict

0x482471ad…122f

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 0x072c7ca81a…50604d

← previous block·next block →recent activity