← previous blocknext block →recent activity

Analyzing

Block #82,523,340

26 transactions · 18 stateful · 2026-06-20 12:30:37 UTC

Parallelism

77/100

Blocked

39%

Avg conflicts / tx

0.81

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #82,523,340  ·  26 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

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x3567cb6a…088f

0x34b655…2a6f

6 touches
3 conflicts

0x1c20587c…6789

0x34b655…2a6f

6 touches
3 conflicts

0x63ce81c4…c889

0x34b655…2a6f

4 touches
1 conflict

0x64e6b875…b276

0x34b655…2a6f

4 touches
1 conflict

0x6f6fc26c…3e34

0x34b655…2a6f

4 touches
1 conflict

0x6fbc2e5a…e69c

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