← previous blocknext block →recent activity

Analyzing

Block #83,617,718

18 transactions · 17 stateful · 2026-06-25 14:24:15 UTC

Parallelism

72/100

Blocked

41%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,617,718  ·  18 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

0xaef9e227…a7ab

0x34b655…2a6f

6 touches
3 conflicts

0xbbb9fa77…d121

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0x019883…2a9a

4 touches
1 conflict

0x00000000…0003

0x019883…2a9a

4 touches
1 conflict

0x44ad89ba…cf83

0x0cc9b2…7777

4 touches
1 conflict

0x99a3a7c1…1e2b

0x0cc9b2…7777

4 touches
1 conflict

0x18978822…2623

0x34b655…2a6f

4 touches
1 conflict

0x286711a5…b3bf

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

3 conflicts on slot 0xaef9e227f0…03a7ab

← previous block·next block →recent activity