← previous blocknext block →recent activity

Analyzing

Block #82,974,697

22 transactions · 20 stateful · 2026-06-22 14:48:06 UTC

Parallelism

73/100

Blocked

35%

Avg conflicts / tx

0.82

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #82,974,697  ·  22 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

12 touches
15 conflicts

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0xf8f1e808…a4fd

0x34b655…2a6f

4 touches
1 conflict

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x3b0a8356…a2b6

0x34b655…2a6f

4 touches
1 conflict

0x41d3bfa5…523e

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity