← previous blocknext block →recent activity

Analyzing

Block #84,362,266

20 transactions · 16 stateful · 2026-06-29 01:07:27 UTC

Parallelism

85/100

Blocked

38%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #84,362,266  ·  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

0xf79df061…e005

0xe52b14…7230

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x5da4ed2f…283f

0xa6afd3…d132

4 touches
1 conflict

0xc05b880b…7746

0xa6afd3…d132

4 touches
1 conflict

0x00000000…0002

0xd637b3…4160

4 touches
1 conflict

0x0b0c2e8d…c1b8

0xe52b14…7230

4 touches
1 conflict

0x532023a5…d800

0xe52b14…7230

4 touches
1 conflict

0x8ffa3328…ce11

0xe52b14…7230

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: 0xe52b1424…bb7230

1 conflict on slot 0xf79df061c7…91e005

← previous block·next block →recent activity