← previous blocknext block →recent activity

Analyzing

Block #83,617,722

23 transactions · 18 stateful · 2026-06-25 14:24:17 UTC

Parallelism

83/100

Blocked

33%

Avg conflicts / tx

0.35

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,617,722  ·  23 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

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xff96dc9b…93d7

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x07b47a10…27ef

0x34b655…2a6f

4 touches
1 conflict

0x022f72c3…07b6

0xc8689a…ee79

4 touches
1 conflict

0x250c3574…21db

0x851145…3f07

4 touches
1 conflict

0xf8ceaa24…6e8e

0x851145…3f07

4 touches
1 conflict

0x65a44266…daa9

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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity