← previous blocknext block →recent activity

Analyzing

Block #103,987,203

21 transactions · 20 stateful · 2026-09-11 20:09:23 UTC

Parallelism

71/100

Blocked

35%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #103,987,203  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x06c469dd…fdfe

0x34b655…2a6f

4 touches
1 conflict

0x100812e9…12b7

0x34b655…2a6f

4 touches
1 conflict

0x21e79ad8…c5db

0x34b655…2a6f

4 touches
1 conflict

0x3243e72f…1f6d

0x34b655…2a6f

4 touches
1 conflict

0x5ad5e6de…e7ad

0x34b655…2a6f

4 touches
1 conflict

0x7aad02c6…b979

0x34b655…2a6f

4 touches
1 conflict

0xb0f5d668…99ac

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity