← previous blocknext block →recent activity

Analyzing

Block #84,199,584

20 transactions · 18 stateful · 2026-06-28 07:03:16 UTC

Parallelism

85/100

Blocked

33%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #84,199,584  ·  20 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xdfc5f346…7b42

0x40c49f…2af0

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x5da4ed2f…283f

0xa6afd3…d132

4 touches
1 conflict

0xc05b880b…7746

0xa6afd3…d132

4 touches
1 conflict

0x6f132c01…cdcd

0x34b655…2a6f

4 touches
1 conflict

0xe99d8e68…a16e

0x34b655…2a6f

4 touches
1 conflict

0x085df2c1…305a

0x34b655…2a6f

2 touches
0 conflicts

0x40970e69…da50

0x69df8a…6292

2 touches
0 conflicts

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: 0x40c49f17…d22af0

1 conflict on slot 0xdfc5f34630…0b7b42

← previous block·next block →recent activity