← previous blocknext block →recent activity

Analyzing

Block #102,841,787

25 transactions · 22 stateful · 2026-09-07 19:53:24 UTC

Parallelism

80/100

Blocked

36%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #102,841,787  ·  25 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xbd590df7…9891

0x34b655…2a6f

8 touches
6 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

8 touches
6 conflicts

0xd66696e0…0842

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf195ad96…e0c3

0x34b655…2a6f

6 touches
3 conflicts

0xfcd5e68f…2a12

0x34b655…2a6f

6 touches
3 conflicts

0xb0f5d668…99ac

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641f

0x34b655…2a6f

6 touches
3 conflicts

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 0xbd590df7f7…cf9891

← previous block·next block →recent activity