← previous blocknext block →recent activity

Analyzing

Block #84,572,890

30 transactions · 15 stateful · 2026-06-30 00:32:15 UTC

Parallelism

83/100

Blocked

40%

Avg conflicts / tx

0.43

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #84,572,890  ·  30 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

0x49194594…2c70

0x34b655…2a6f

8 touches
6 conflicts

0xd89f212d…2bbf

0x34b655…2a6f

8 touches
6 conflicts

0x25de453d…9573

0x34b655…2a6f

4 touches
1 conflict

0x6f1a10f8…5a04

0x34b655…2a6f

4 touches
1 conflict

0x78154eae…fae7

0x34b655…2a6f

4 touches
1 conflict

0x781a2c9b…f540

0x34b655…2a6f

4 touches
1 conflict

0x7cb2f3fa…4836

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