← previous blocknext block →recent activity

Analyzing

Block #83,662,043

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

Parallelism

83/100

Blocked

29%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,662,043  ·  24 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xe99d8e68…a16e

0x34b655…2a6f

8 touches
6 conflicts

0x9b58e20f…2dd9

0x34b655…2a6f

6 touches
3 conflicts

0x95cb8e34…5eba

0x34b655…2a6f

6 touches
3 conflicts

0xf324b405…ca30

0x34b655…2a6f

6 touches
3 conflicts

0x022f72c3…07b6

0xc8689a…ee79

6 touches
3 conflicts

0x3405238a…68b6

0x34b655…2a6f

4 touches
1 conflict

0x4aec7a7e…3b31

0x34b655…2a6f

4 touches
1 conflict

0x6108bb21…3259

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

6 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity