← previous blocknext block →recent activity

Analyzing

Block #84,079,215

25 transactions · 24 stateful · 2026-06-27 17:41:48 UTC

Parallelism

68/100

Blocked

54%

Avg conflicts / tx

1.6

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #84,079,215  ·  25 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x00000000…0002

0xd637b3…4160

16 touches
28 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

8 touches
6 conflicts

0xe02484a6…c32e

0xc8689a…ee79

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xdf708ee7…1fcf

0xc8689a…ee79

6 touches
3 conflicts

0x15c9b5bf…f732

0x34b655…2a6f

6 touches
3 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

6 touches
3 conflicts

0x8cf3d245…1d0d

0x69df8a…6292

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: 0xd637b38f…c64160

28 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity