← previous blocknext block →recent activity

Analyzing

Block #84,499,397

20 transactions · 18 stateful · 2026-06-29 16:21:40 UTC

Parallelism

80/100

Blocked

39%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #84,499,397  ·  20 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

0xe99d8e68…a16e

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x0110331c…b891

0x34b655…2a6f

4 touches
1 conflict

0x7dc64b2c…05e7

0x34b655…2a6f

4 touches
1 conflict

0xb1993ff2…a1cf

0x34b655…2a6f

4 touches
1 conflict

0xba7edbee…7e5d

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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 0xe99d8e683a…2ea16e

← previous block·next block →recent activity