← previous blocknext block →recent activity

Analyzing

Block #74,761,115

17 transactions · 13 stateful · 2026-05-15 13:32:29 UTC

Parallelism

82/100

Blocked

31%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,761,115  ·  17 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

0xb9868b52…c77f

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x3254d19b…f714

0x34b655…2a6f

2 touches
0 conflicts

0x38c47502…1005

0x34b655…2a6f

2 touches
0 conflicts

0x3e1f7818…2fc8

0x34b655…2a6f

2 touches
0 conflicts

0x50defdf6…eb3c

0x34b655…2a6f

2 touches
0 conflicts

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: 0x34b6552d…112a6f

3 conflicts on slot 0xb9868b5233…c6c77f

← previous block·next block →recent activity