← previous blocknext block →recent activity

Analyzing

Block #82,021,611

20 transactions · 17 stateful · 2026-06-18 04:44:05 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.95

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #82,021,611  ·  20 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

0x00000000…0002

0xaa7ee7…f0e4

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x21898044…a071

0x065c9d…c394

6 touches
3 conflicts

0xd9d409a5…d9cf

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001b

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: 0xaa7ee7ce…aff0e4

10 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity