← previous blocknext block →recent activity

Analyzing

Block #84,305,280

16 transactions · 15 stateful · 2026-06-28 18:47:38 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #84,305,280  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xe99d8e68…a16e

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0xa9db7b4d…2957

0x40c49f…2af0

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x0d35e1ad…b4d6

0x34b655…2a6f

4 touches
1 conflict

0x1ca68aab…5e4a

0x34b655…2a6f

4 touches
1 conflict

0x1e346a85…e9c5

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

1 conflict on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity