← previous blocknext block →recent activity

Analyzing

Block #84,074,207

23 transactions · 19 stateful · 2026-06-27 17:08:23 UTC

Parallelism

87/100

Blocked

32%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #84,074,207  ·  23 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

0x49194594…2c70

0x34b655…2a6f

6 touches
3 conflicts

0xd16df6cd…5532

0x40c49f…2af0

6 touches
3 conflicts

0xe02484a6…c32e

0xc8689a…ee79

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x5581d709…ab77

0x2a68ba…90c5

4 touches
1 conflict

0x15c9b5bf…f732

0x34b655…2a6f

4 touches
1 conflict

0x19ce481d…6c36

0x34b655…2a6f

4 touches
1 conflict

0x9c21fea5…4479

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

3 conflicts on slot 0x4919459402…d42c70

← previous block·next block →recent activity