← previous blocknext block →recent activity

Analyzing

Block #84,511,349

18 transactions · 16 stateful · 2026-06-29 17:41:26 UTC

Parallelism

72/100

Blocked

44%

Avg conflicts / tx

0.61

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #84,511,349  ·  18 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

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x170e4e4c…2b90

0x34b655…2a6f

4 touches
1 conflict

0x274b85f7…c526

0x34b655…2a6f

4 touches
1 conflict

0x3da49e5d…8067

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4a79bfea…bc8d

0x34b655…2a6f

4 touches
1 conflict

0x67c47060…795d

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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity