← previous blocknext block →recent activity

Analyzing

Block #84,278,595

21 transactions · 18 stateful · 2026-06-28 15:49:47 UTC

Parallelism

81/100

Blocked

39%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #84,278,595  ·  21 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x454d8940…cfe7

0x34b655…2a6f

6 touches
3 conflicts

0x05cd9288…8acf

0x065c9d…c394

5 touches
3 conflicts

0x284afa64…a5d7

0x34b655…2a6f

4 touches
1 conflict

0x2965e2d6…5800

0x34b655…2a6f

4 touches
1 conflict

0x2c53a187…3646

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity