← previous blocknext block →recent activity

Analyzing

Block #82,341,363

26 transactions · 17 stateful · 2026-06-19 16:16:39 UTC

Parallelism

81/100

Blocked

41%

Avg conflicts / tx

0.62

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #82,341,363  ·  26 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0xb2fa1675…4e07

0x34b655…2a6f

8 touches
6 conflicts

0xe2142951…6af0

0x34b655…2a6f

6 touches
3 conflicts

0x4d143d3d…5331

0x34b655…2a6f

6 touches
3 conflicts

0x08913286…f0df

0x34b655…2a6f

6 touches
3 conflicts

0x6bc390fc…126b

0x34b655…2a6f

4 touches
1 conflict

0x73f16822…0338

0x34b655…2a6f

4 touches
1 conflict

0x793aa64d…b09c

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

10 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity