← previous blocknext block →recent activity

Analyzing

Block #83,401,007

18 transactions · 17 stateful · 2026-06-24 14:18:00 UTC

Parallelism

83/100

Blocked

41%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #83,401,007  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x2004b5f1…ff98

0x34b655…2a6f

6 touches
3 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

6 touches
3 conflicts

0x022f72c3…07b6

0xc8689a…ee79

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x01179535…e4e8

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x264f234b…3bc2

0x34b655…2a6f

4 touches
1 conflict

0xef3a4217…dec8

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

3 conflicts on slot 0x2004b5f102…a7ff98

← previous block·next block →recent activity