← previous blocknext block →recent activity

Analyzing

Block #102,243,129

23 transactions · 21 stateful · 2026-09-05 17:24:13 UTC

Parallelism

70/100

Blocked

38%

Avg conflicts / tx

0.87

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #102,243,129  ·  23 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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x5da92df7…74b5

0x34b655…2a6f

6 touches
3 conflicts

0x839c0c71…bada

0x34b655…2a6f

6 touches
3 conflicts

0x820d7282…6c34

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x06afe596…21f2

0x34b655…2a6f

6 touches
3 conflicts

0x4c7c2471…43d7

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 0xc824469a90…af6425

← previous block·next block →recent activity