← previous blocknext block →recent activity

Analyzing

Block #83,626,910

50 transactions · 36 stateful · 2026-06-25 15:25:42 UTC

Parallelism

80/100

Blocked

64%

Avg conflicts / tx

1.44

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #83,626,910  ·  50 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

18 touches
36 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

12 touches
15 conflicts

0xdb19247d…233c

0x34b655…2a6f

10 touches
10 conflicts

0x5fad6fee…7714

0x34b655…2a6f

10 touches
10 conflicts

0x31aa2853…8dbb

0xc8689a…ee79

10 touches
10 conflicts

0x10c19272…7442

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x7534f53d…6ed4

0x34b655…2a6f

8 touches
6 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

36 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity