← previous blocknext block →recent activity

Analyzing

Block #74,332,290

33 transactions · 24 stateful · 2026-05-13 13:48:06 UTC

Parallelism

85/100

Blocked

46%

Avg conflicts / tx

0.82

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,332,290  ·  33 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x6af306bb…2e81

0x3bd359…433a

8 touches
6 conflicts

0xf91b744e…9117

0x754704…b603

8 touches
6 conflicts

0xce8bbe33…b72e

0x3bd359…433a

8 touches
6 conflicts

0x0ce6e18e…f7ce

0xd32edf…ff58

7 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x1c389468…6b0e

0x34b655…2a6f

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

10 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity