← previous blocknext block →recent activity

Analyzing

Block #83,659,062

21 transactions · 20 stateful · 2026-06-25 19:00:21 UTC

Parallelism

67/100

Blocked

35%

Avg conflicts / tx

0.86

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #83,659,062  ·  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

0xd2453506…54e4

0x34b655…2a6f

6 touches
3 conflicts

0x571cb36d…3b3d

0x34b655…2a6f

6 touches
3 conflicts

0x17cc5ec3…ae0e

0x34b655…2a6f

6 touches
3 conflicts

0x3a61096b…5107

0x34b655…2a6f

4 touches
1 conflict

0x5d7f309d…5145

0x34b655…2a6f

4 touches
1 conflict

0x5f3fc680…f989

0x34b655…2a6f

4 touches
1 conflict

0x74fd0a9b…3aaa

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