← previous blocknext block →recent activity

Analyzing

Block #83,957,141

20 transactions · 17 stateful · 2026-06-27 04:08:35 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.85

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,957,141  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x8c09fdbf…2abc

0x34b655…2a6f

6 touches
3 conflicts

0xa02e5cdd…76b8

0x34b655…2a6f

6 touches
3 conflicts

0x08cc68a2…2a59

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x26c6d946…6676

0x34b655…2a6f

4 touches
1 conflict

0x6b47245e…a342

0x34b655…2a6f

4 touches
1 conflict

0x74fd0a9b…3aaa

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