← previous blocknext block →recent activity

Analyzing

Block #102,524,241

20 transactions · 20 stateful · 2026-09-06 17:08:44 UTC

Parallelism

65/100

Blocked

40%

Avg conflicts / tx

0.75

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #102,524,241  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x247cfb80…cca8

0x34b655…2a6f

6 touches
3 conflicts

0x990354fe…cef2

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xb75367ff…a2b7

0x34b655…2a6f

6 touches
3 conflicts

0x165fe1f0…859f

0x34b655…2a6f

6 touches
3 conflicts

0x94e7f277…471b

0x34b655…2a6f

4 touches
1 conflict

0xab7f4e6b…8093

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 0x247cfb80ae…c4cca8

← previous block·next block →recent activity