← previous blocknext block →recent activity

Analyzing

Block #84,332,502

20 transactions · 18 stateful · 2026-06-28 21:48:59 UTC

Parallelism

65/100

Blocked

44%

Avg conflicts / tx

0.85

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #84,332,502  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xcfe15fba…4f97

0x34b655…2a6f

10 touches
10 conflicts

0x31aa2853…8dbb

0xc8689a…ee79

8 touches
6 conflicts

0x0833f1ab…71e7

0x34b655…2a6f

8 touches
6 conflicts

0x98d3fc79…df78

0x34b655…2a6f

8 touches
6 conflicts

0xae0f3b1e…c3e1

0x34b655…2a6f

8 touches
6 conflicts

0xb6ed511f…6b68

0x34b655…2a6f

8 touches
6 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

8 touches
6 conflicts

0x7c6984da…21e5

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 0xcfe15fbaf6…e24f97

← previous block·next block →recent activity