← previous blocknext block →recent activity

Analyzing

Block #84,142,012

17 transactions · 12 stateful · 2026-06-28 00:40:07 UTC

Parallelism

88/100

Blocked

17%

Avg conflicts / tx

0.12

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #84,142,012  ·  17 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xf4b4898d…f948

0x34b655…2a6f

4 touches
1 conflict

0x5d7f309d…5145

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f0

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f1

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x137a69a8…8b93

0x34b655…2a6f

3 touches
1 conflict

0x4ec9ff52…e6f7

0x34b655…2a6f

2 touches
0 conflicts

0x4f4bdabd…ffba

0x34b655…2a6f

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: Perpl

1 conflict on slot 0xf4b4898d2f…34f948

← previous block·next block →recent activity