← previous blocknext block →recent activity

Analyzing

Block #83,656,348

26 transactions · 20 stateful · 2026-06-25 18:42:14 UTC

Parallelism

81/100

Blocked

40%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,656,348  ·  26 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xbd68c7c7…40b3

0x34b655…2a6f

8 touches
6 conflicts

0x76477ddf…b8f8

0xc8689a…ee79

6 touches
3 conflicts

0xf06c2cf5…61bd

0x34b655…2a6f

6 touches
3 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

6 touches
3 conflicts

0x0ce40347…2c5d

0x34b655…2a6f

6 touches
3 conflicts

0x6767aeb1…eabc

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0b16149e…7d4d

0x065c9d…c394

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 0xbd68c7c758…bd40b3

← previous block·next block →recent activity