← previous blocknext block →recent activity

Analyzing

Block #83,967,382

17 transactions · 16 stateful · 2026-06-27 05:16:50 UTC

Parallelism

82/100

Blocked

44%

Avg conflicts / tx

0.59

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #83,967,382  ·  17 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x45168a17…c631

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xa37d59c6…996b

0x34b655…2a6f

4 touches
1 conflict

0xb99958f6…ccf0

0x34b655…2a6f

4 touches
1 conflict

0xb99958f6…ccf1

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity