← previous blocknext block →recent activity

Analyzing

Block #84,246,446

30 transactions · 18 stateful · 2026-06-28 12:15:40 UTC

Parallelism

80/100

Blocked

44%

Avg conflicts / tx

0.63

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #84,246,446  ·  30 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0xe1e58d05…117f

0x34b655…2a6f

8 touches
6 conflicts

0x0efc210e…70ab

0x34b655…2a6f

8 touches
6 conflicts

0x31aa2853…8dbb

0xc8689a…ee79

8 touches
6 conflicts

0xb6c88e49…7bbf

0x34b655…2a6f

7 touches
6 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x40970e69…da50

0x69df8a…6292

4 touches
1 conflict

0x8cf3d245…1d0d

0x69df8a…6292

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

15 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity