← previous blocknext block →recent activity

Analyzing

Block #82,977,213

25 transactions · 17 stateful · 2026-06-22 15:04:54 UTC

Parallelism

84/100

Blocked

41%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #82,977,213  ·  25 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x9f287382…28e5

0x34b655…2a6f

4 touches
1 conflict

0xa1830b71…6cd6

0x34b655…2a6f

4 touches
1 conflict

0xa2dd7133…24d0

0x34b655…2a6f

4 touches
1 conflict

0xe283e878…7262

0x34b655…2a6f

4 touches
1 conflict

0xedf4636f…b2a2

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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

← previous block·next block →recent activity