← previous blocknext block →recent activity

Analyzing

Block #79,115,139

23 transactions · 19 stateful · 2026-06-04 17:33:23 UTC

Parallelism

83/100

Blocked

37%

Avg conflicts / tx

0.74

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #79,115,139  ·  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

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x9ea94a10…15e7

0x065c9d…c394

5 touches
3 conflicts

0xcbdccf41…ab3d

0x065c9d…c394

4 touches
1 conflict

0xca0f0668…caf3

0xa6afd3…d132

4 touches
1 conflict

0x9ff176a9…152e

0x065c9d…c394

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: 0xa6afd386…b0d132

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity