← previous blocknext block →recent activity

Analyzing

Block #81,834,257

21 transactions · 16 stateful · 2026-06-17 07:53:17 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

0.76

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #81,834,257  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xf6d214b0…8abe

0x34b655…2a6f

6 touches
3 conflicts

0x4360b49f…140d

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xb6bc6efb…ad9b

0x34b655…2a6f

5 touches
3 conflicts

0x915c095e…c1e5

0x69df8a…6292

4 touches
1 conflict

0xcfe06a18…b5b5

0x69df8a…6292

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity