← previous blocknext block →recent activity

Analyzing

Block #83,660,477

27 transactions · 24 stateful · 2026-06-25 19:09:45 UTC

Parallelism

85/100

Blocked

29%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,660,477  ·  27 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

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x022f72c3…07b6

0xc8689a…ee79

6 touches
3 conflicts

0x2a513dfb…2bb8

0x34b655…2a6f

6 touches
3 conflicts

0x6ac6d1bf…8b19

0x34b655…2a6f

6 touches
3 conflicts

0x7ee6007b…fd68

0x34b655…2a6f

6 touches
3 conflicts

0x8e6f14d7…df22

0x34b655…2a6f

6 touches
3 conflicts

0x9b58e20f…2dd9

0x34b655…2a6f

6 touches
3 conflicts

0xd1e7ce0a…7f3b

0x34b655…2a6f

6 touches
3 conflicts

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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity