← previous blocknext block →recent activity

Analyzing

Block #84,400,743

23 transactions · 19 stateful · 2026-06-29 05:23:57 UTC

Parallelism

83/100

Blocked

32%

Avg conflicts / tx

0.3

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #84,400,743  ·  23 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xda7f9bd2…e332

0x34b655…2a6f

4 touches
1 conflict

0xec85756f…0ba2

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0xdfc5f346…7b42

0x40c49f…2af0

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x5581d709…ab77

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xb3fb9fb5…64db

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

1 conflict on slot 0xda7f9bd20d…e9e332

← previous block·next block →recent activity