← previous blocknext block →recent activity

Analyzing

Block #83,453,300

21 transactions · 17 stateful · 2026-06-24 20:07:20 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,453,300  ·  21 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

0xe99d8e68…a16e

0x34b655…2a6f

10 touches
10 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x31aa2853…8dbb

0xc8689a…ee79

4 touches
1 conflict

0x731e6d82…2883

0x065c9d…c394

4 touches
1 conflict

0xbb3504d4…b05f

0x34b655…2a6f

4 touches
1 conflict

0xdf37a93d…879b

0x34b655…2a6f

4 touches
1 conflict

0xe1593d74…b99c

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

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

10 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity