← previous blocknext block →recent activity

Analyzing

Block #74,775,085

16 transactions · 13 stateful · 2026-05-15 15:06:06 UTC

Parallelism

81/100

Blocked

38%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,775,085  ·  16 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x489cb750…7069

0x065c9d…c394

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xa472d565…9fe4

0x3bd359…433a

4 touches
1 conflict

0xaadf42dc…f433

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0x7d0364…a52b

4 touches
1 conflict

0x00000000…0001

0x7d0364…a52b

4 touches
1 conflict

0x131ec7f4…baaf

0xaca864…7777

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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity