← previous blocknext block →recent activity

Analyzing

Block #83,398,831

21 transactions · 15 stateful · 2026-06-24 14:03:27 UTC

Parallelism

81/100

Blocked

40%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,398,831  ·  21 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

0x758bd24b…cc0c

0x34b655…2a6f

8 touches
6 conflicts

0x0835adb5…ad83

0x34b655…2a6f

6 touches
3 conflicts

0x18742fec…b224

0x34b655…2a6f

4 touches
1 conflict

0x213a54fa…c85f

0x34b655…2a6f

4 touches
1 conflict

0x8b305a3b…1c35

0x34b655…2a6f

4 touches
1 conflict

0x9c7571b3…9605

0x34b655…2a6f

4 touches
1 conflict

0xa1571d54…ae41

0x34b655…2a6f

4 touches
1 conflict

0xe99d8e68…a16e

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

6 conflicts on slot 0x758bd24bd8…71cc0c

← previous block·next block →recent activity