← previous blocknext block →recent activity

Analyzing

Block #74,492,277

26 transactions · 24 stateful · 2026-05-14 07:32:52 UTC

Parallelism

69/100

Blocked

42%

Avg conflicts / tx

1.19

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,492,277  ·  26 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

0xab3526…fa38

16 touches
28 conflicts

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xa4df9ac6…abb9

0xd32edf…ff58

3 touches
1 conflict

0x00f7e3b7…e017

0x188d58…ea8e

2 touches
0 conflicts

0x06cdf7f0…fbe6

0x3bd359…433a

2 touches
0 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

2 touches
0 conflicts

0x00000000…0000

0x63e48b…53f2

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: 0xab35264b…1cfa38

28 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity