← previous blocknext block →recent activity

Analyzing

Block #83,201,651

22 transactions · 21 stateful · 2026-06-23 16:06:11 UTC

Parallelism

77/100

Blocked

38%

Avg conflicts / tx

0.73

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,201,651  ·  22 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

0x342fbbca…d443

0x40c49f…2af0

8 touches
6 conflicts

0x00000000…003d

0x40c49f…2af0

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001a

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002a

0x1b6862…e19c

4 touches
1 conflict

0x92d84c1c…f472

0x40c49f…2af0

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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: 0x40c49f17…d22af0

6 conflicts on slot 0x342fbbca09…fcd443

← previous block·next block →recent activity