← previous blocknext block →recent activity

Analyzing

Block #81,481,440

19 transactions · 16 stateful · 2026-06-15 16:42:53 UTC

Parallelism

79/100

Blocked

38%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #81,481,440  ·  19 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

0x96047c45…b64a

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x9495fb50…b6e8

0x34b655…2a6f

4 touches
1 conflict

0x97785d36…2ac5

0x34b655…2a6f

4 touches
1 conflict

0xa4e5e0c2…6e04

0x34b655…2a6f

4 touches
1 conflict

0xaf78779d…317d

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf324b405…ca30

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 0x96047c45d5…89b64a

← previous block·next block →recent activity