← previous blocknext block →recent activity

Analyzing

Block #83,638,915

18 transactions · 17 stateful · 2026-06-25 16:45:55 UTC

Parallelism

61/100

Blocked

47%

Avg conflicts / tx

1.17

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #83,638,915  ·  18 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

0xbb3504d4…b05f

0x34b655…2a6f

10 touches
10 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0x049cca71…b102

0x34b655…2a6f

10 touches
10 conflicts

0xa7c77c66…e76d

0x34b655…2a6f

8 touches
6 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

8 touches
6 conflicts

0xf324b405…ca30

0x34b655…2a6f

8 touches
6 conflicts

0x9f715341…353a

0x34b655…2a6f

6 touches
3 conflicts

0xdc8d4ee0…def3

0x34b655…2a6f

6 touches
3 conflicts

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 0xbb3504d4cd…acb05f

← previous block·next block →recent activity