← previous blocknext block →recent activity

Analyzing

Block #83,411,304

20 transactions · 18 stateful · 2026-06-24 15:26:47 UTC

Parallelism

80/100

Blocked

39%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,411,304  ·  20 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

0x31aa2853…8dbb

0xc8689a…ee79

6 touches
3 conflicts

0x4ec9ff52…e6f7

0x34b655…2a6f

6 touches
3 conflicts

0xd406be52…9094

0x34b655…2a6f

6 touches
3 conflicts

0xfebf4166…9bf2

0x34b655…2a6f

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

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