← previous blocknext block →recent activity

Analyzing

Block #84,572,995

20 transactions · 17 stateful · 2026-06-30 00:32:57 UTC

Parallelism

70/100

Blocked

47%

Avg conflicts / tx

0.85

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #84,572,995  ·  20 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

8 touches
6 conflicts

0xf1e0175c…5649

0x34b655…2a6f

8 touches
6 conflicts

0xd99b3b64…1c95

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x329f2f7d…dcff

0x34b655…2a6f

4 touches
1 conflict

0x335892bb…ae71

0x34b655…2a6f

4 touches
1 conflict

0x339fca69…8fd8

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity