← previous blocknext block →recent activity

Analyzing

Block #82,262,489

20 transactions · 16 stateful · 2026-06-19 07:30:27 UTC

Parallelism

80/100

Blocked

50%

Avg conflicts / tx

0.7

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #82,262,489  ·  20 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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x342fbbca…d443

0x40c49f…2af0

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x87ee379a…cd9e

0x34b655…2a6f

6 touches
3 conflicts

0xda46a376…f6a6

0x34b655…2a6f

6 touches
3 conflicts

0x0efc210e…70ab

0x34b655…2a6f

4 touches
1 conflict

0x1d6cb721…c88c

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 0xc824469a90…af6425

← previous block·next block →recent activity