← previous blocknext block →recent activity

Analyzing

Block #84,494,296

25 transactions · 21 stateful · 2026-06-29 15:47:38 UTC

Parallelism

72/100

Blocked

38%

Avg conflicts / tx

0.44

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #84,494,296  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xd637b3…4160

4 touches
1 conflict

0xe75cebb6…6b36

0x065c9d…c394

4 touches
1 conflict

0x5c591136…d322

0x34b655…2a6f

4 touches
1 conflict

0xa5f1d2ef…822e

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 0x737acb7813…fafce8

← previous block·next block →recent activity