← previous blocknext block →recent activity

Analyzing

Block #84,522,485

19 transactions · 17 stateful · 2026-06-29 18:55:41 UTC

Parallelism

79/100

Blocked

35%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #84,522,485  ·  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

0xbd68c7c7…40b3

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xe75cebb6…6b36

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0xd637b3…4160

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x56785e37…a197

0x065c9d…c394

4 touches
1 conflict

0x2877f440…c2c8

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 0xbd68c7c758…bd40b3

← previous block·next block →recent activity