← previous blocknext block →recent activity

Analyzing

Block #83,759,611

17 transactions · 13 stateful · 2026-06-26 06:11:06 UTC

Parallelism

82/100

Blocked

46%

Avg conflicts / tx

0.41

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #83,759,611  ·  17 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

0xffc2f21e…b393

0x34b655…2a6f

6 touches
3 conflicts

0xe02484a6…c32e

0xc8689a…ee79

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x2484cc15…5afc

0x34b655…2a6f

4 touches
1 conflict

0x5941ac48…c525

0x34b655…2a6f

4 touches
1 conflict

0x8190162b…5c4b

0x34b655…2a6f

4 touches
1 conflict

0xe99d8e68…a16e

0x34b655…2a6f

4 touches
1 conflict

0xfc53f931…cba0

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 0xffc2f21efe…ecb393

← previous block·next block →recent activity