← previous blocknext block →recent activity

Analyzing

Block #83,639,629

19 transactions · 16 stateful · 2026-06-25 16:50:41 UTC

Parallelism

79/100

Blocked

44%

Avg conflicts / tx

0.68

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,639,629  ·  19 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

0xbd68c7c7…40b3

0x34b655…2a6f

8 touches
6 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

6 touches
3 conflicts

0xbfe63d66…c3e6

0x34b655…2a6f

6 touches
3 conflicts

0x7e17e82a…9748

0x34b655…2a6f

4 touches
1 conflict

0x7e6c970a…65af

0x34b655…2a6f

4 touches
1 conflict

0xb1c67a7d…b9b1

0x34b655…2a6f

4 touches
1 conflict

0x022f72c3…07b6

0xc8689a…ee79

4 touches
1 conflict

0x13a54fa2…5ae3

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 0xbd68c7c758…bd40b3

← previous block·next block →recent activity