← previous blocknext block →recent activity

Analyzing

Block #83,466,792

18 transactions · 15 stateful · 2026-06-24 21:37:29 UTC

Parallelism

72/100

Blocked

53%

Avg conflicts / tx

0.61

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,466,792  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x46d5a052…ff2e

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x4e7eb462…b2aa

0x1b6862…e19c

4 touches
1 conflict

0x044970ef…19c9

0x34b655…2a6f

4 touches
1 conflict

0x0ad4dbe8…ae93

0x34b655…2a6f

4 touches
1 conflict

0x1c48b3ac…a03c

0x34b655…2a6f

4 touches
1 conflict

0x2297af12…c668

0x34b655…2a6f

4 touches
1 conflict

0x2c539d94…b63a

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 0x46d5a0529d…adff2e

← previous block·next block →recent activity