← previous blocknext block →recent activity

Analyzing

Block #102,248,023

20 transactions · 20 stateful · 2026-09-05 17:49:00 UTC

Parallelism

80/100

Blocked

35%

Avg conflicts / tx

0.65

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #102,248,023  ·  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

0x145a7027…e71a

0x34b655…2a6f

8 touches
6 conflicts

0x820d7282…6c34

0x34b655…2a6f

6 touches
3 conflicts

0x5d1ac445…5233

0x34b655…2a6f

6 touches
3 conflicts

0xd17580f9…ece1

0x754704…b603

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x152f8e3d…3da0

0x34b655…2a6f

4 touches
1 conflict

0x24ed74ea…a3ff

0x34b655…2a6f

4 touches
1 conflict

0x4b193211…33f4

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

6 conflicts on slot 0x145a702793…69e71a

← previous block·next block →recent activity