← previous blocknext block →recent activity

Analyzing

Block #74,382,816

32 transactions · 27 stateful · 2026-05-13 19:24:15 UTC

Parallelism

69/100

Blocked

59%

Avg conflicts / tx

1.25

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,382,816  ·  32 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x60f7fbaf…bd58

0x34b655…2a6f

14 touches
21 conflicts

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0xa02838a3…bc54

0x34b655…2a6f

6 touches
3 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xb40c0e83…0277

0xd32edf…ff58

5 touches
3 conflicts

0x8902ba1f…f4b6

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

21 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity