← previous blocknext block →recent activity

Analyzing

Block #84,318,341

23 transactions · 20 stateful · 2026-06-28 20:14:35 UTC

Parallelism

74/100

Blocked

40%

Avg conflicts / tx

0.65

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #84,318,341  ·  23 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

0xe99d8e68…a16e

0x34b655…2a6f

8 touches
6 conflicts

0x32229dd3…4dbb

0x34b655…2a6f

6 touches
3 conflicts

0xffc2f21e…b393

0x34b655…2a6f

6 touches
3 conflicts

0xfa5537f3…0ef2

0x065c9d…c394

4 touches
1 conflict

0x76477ddf…b8f8

0xc8689a…ee79

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xe75cebb6…6b36

0x065c9d…c394

4 touches
1 conflict

0x6acc4afc…e7db

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 0xe99d8e683a…2ea16e

← previous block·next block →recent activity