← previous blocknext block →recent activity

Analyzing

Block #83,978,831

19 transactions · 17 stateful · 2026-06-27 06:33:07 UTC

Parallelism

84/100

Blocked

29%

Avg conflicts / tx

0.37

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #83,978,831  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x9672a430…3356

0x34b655…2a6f

6 touches
3 conflicts

0x18b11fba…c92a

0x34b655…2a6f

4 touches
1 conflict

0x206f4379…e08a

0x34b655…2a6f

4 touches
1 conflict

0x3c639b4c…1e8d

0x34b655…2a6f

4 touches
1 conflict

0x4ec9ff52…e6f7

0x34b655…2a6f

4 touches
1 conflict

0x7d0beae0…eb6e

0x34b655…2a6f

4 touches
1 conflict

0x8f2f9e67…3be0

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity