← previous blocknext block →recent activity

Analyzing

Block #102,249,378

20 transactions · 18 stateful · 2026-09-05 17:55:50 UTC

Parallelism

80/100

Blocked

39%

Avg conflicts / tx

0.7

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #102,249,378  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x9e40ae1f…d997

0x34b655…2a6f

6 touches
3 conflicts

0x76e02d19…7609

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0x179b31b3…6dd2

0x34b655…2a6f

6 touches
3 conflicts

0xda17b98d…c3e1

0x34b655…2a6f

6 touches
3 conflicts

0x611baab2…2400

0x34b655…2a6f

4 touches
1 conflict

0x65f011a5…bc6e

0x34b655…2a6f

4 touches
1 conflict

0x045532dd…4b7d

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 0x9e40ae1f7f…8cd997

← previous block·next block →recent activity