← previous blocknext block →recent activity

Analyzing

Block #82,721,527

18 transactions · 17 stateful · 2026-06-21 10:36:44 UTC

Parallelism

78/100

Blocked

47%

Avg conflicts / tx

0.83

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #82,721,527  ·  18 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

0x00000000…003d

0x40c49f…2af0

8 touches
6 conflicts

0x76d1e78d…7877

0x40c49f…2af0

6 touches
3 conflicts

0x5d46e6a0…5ed9

0x40c49f…2af0

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x5581d709…ab77

0x2a68ba…90c5

4 touches
1 conflict

0xfecb18c0…01ed

0x34b655…2a6f

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x6754816b…956f

0xd32edf…ff58

3 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 0x0000000000…00003d

← previous block·next block →recent activity