← previous blocknext block →recent activity

Analyzing

Block #83,633,418

21 transactions · 19 stateful · 2026-06-25 16:09:11 UTC

Parallelism

67/100

Blocked

47%

Avg conflicts / tx

1.1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #83,633,418  ·  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

0xffc2f21e…b393

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0x63c900f4…2600

0x34b655…2a6f

6 touches
3 conflicts

0x8c73d3c9…94fd

0x34b655…2a6f

4 touches
1 conflict

0x9a573905…60cf

0x34b655…2a6f

4 touches
1 conflict

0x9b58e20f…2dd9

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

15 conflicts on slot 0xffc2f21efe…ecb393

← previous block·next block →recent activity