← previous blocknext block →recent activity

Analyzing

Block #84,333,071

18 transactions · 13 stateful · 2026-06-28 21:52:44 UTC

Parallelism

78/100

Blocked

54%

Avg conflicts / tx

0.83

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #84,333,071  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xfd4e2262…cd8c

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x37a276a3…673f

0x34b655…2a6f

4 touches
1 conflict

0x75194ada…a1c5

0x34b655…2a6f

4 touches
1 conflict

0x7cb2f3fa…4836

0x34b655…2a6f

4 touches
1 conflict

0x830bee06…a264

0x34b655…2a6f

4 touches
1 conflict

0x85ae9109…fc13

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