← previous blocknext block →recent activity

Analyzing

Block #83,454,939

21 transactions · 20 stateful · 2026-06-24 20:18:18 UTC

Parallelism

67/100

Blocked

40%

Avg conflicts / tx

0.81

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #83,454,939  ·  21 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x8b61212e…558e

0x34b655…2a6f

8 touches
6 conflicts

0x10a2bf7d…caf7

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad04

0x34b655…2a6f

4 touches
1 conflict

0x37674bd8…8f35

0x34b655…2a6f

4 touches
1 conflict

0x3b0a8356…a2b6

0x34b655…2a6f

4 touches
1 conflict

0x3ec82b22…1f46

0x34b655…2a6f

4 touches
1 conflict

0x537e2e5b…c3ab

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity