← previous blocknext block →recent activity

Analyzing

Block #84,488,296

21 transactions · 20 stateful · 2026-06-29 15:07:35 UTC

Parallelism

76/100

Blocked

35%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #84,488,296  ·  21 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

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xbb96f8af…205f

0x34b655…2a6f

6 touches
3 conflicts

0x3d4e9c61…9677

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xafd867b7…2b2d

0x34b655…2a6f

4 touches
1 conflict

0xc08d4b61…1299

0x34b655…2a6f

4 touches
1 conflict

0xca3cdc4f…1f8b

0x34b655…2a6f

4 touches
1 conflict

0xe181f491…f4e3

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 0xac2a02739b…81721b

← previous block·next block →recent activity