← previous blocknext block →recent activity

Analyzing

Block #84,499,380

19 transactions · 17 stateful · 2026-06-29 16:21:33 UTC

Parallelism

79/100

Blocked

35%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #84,499,380  ·  19 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

0x7dc64b2c…05e7

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xab86573c…682e

0x34b655…2a6f

6 touches
3 conflicts

0x2666137c…e4ea

0x34b655…2a6f

4 touches
1 conflict

0x329f2f7d…dcff

0x34b655…2a6f

4 touches
1 conflict

0x3c3d6fd2…0d28

0x34b655…2a6f

4 touches
1 conflict

0x4b309bdb…ccbb

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

3 conflicts on slot 0x7dc64b2c34…6405e7

← previous block·next block →recent activity