← previous blocknext block →recent activity

Analyzing

Block #82,293,024

23 transactions · 18 stateful · 2026-06-19 10:54:13 UTC

Parallelism

70/100

Blocked

50%

Avg conflicts / tx

0.78

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #82,293,024  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x75959b84…9bda

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

6 touches
3 conflicts

0x3214fb6a…0f14

0x34b655…2a6f

4 touches
1 conflict

0x8a659db4…eb14

0x34b655…2a6f

4 touches
1 conflict

0x9a5dbf03…856f

0x34b655…2a6f

4 touches
1 conflict

0xaf78779d…317d

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

← previous block·next block →recent activity