← previous blocknext block →recent activity

Analyzing

Block #83,616,819

25 transactions · 20 stateful · 2026-06-25 14:18:14 UTC

Parallelism

76/100

Blocked

40%

Avg conflicts / tx

0.64

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #83,616,819  ·  25 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

10 touches
10 conflicts

0xffc2f21e…b393

0x34b655…2a6f

6 touches
3 conflicts

0x8d0e98f3…7ba0

0x34b655…2a6f

6 touches
3 conflicts

0x6ff7b857…4985

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…002b

0x1b6862…e19c

4 touches
1 conflict

0xb0e4f69d…34e4

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x003707e5…3f11

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity