← previous blocknext block →recent activity

Analyzing

Block #74,805,402

25 transactions · 16 stateful · 2026-05-15 18:28:35 UTC

Parallelism

64/100

Blocked

56%

Avg conflicts / tx

1.48

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,805,402  ·  25 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x9a0a8bbf…e75b

0xd32edf…ff58

17 touches
36 conflicts

0xb1526c23…f2b7

0x1b6862…e19c

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001b

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002b

0x1b6862…e19c

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: 0xd32edf66…9fff58

36 conflicts on slot 0x9a0a8bbfa6…2fe75b

← previous block·next block →recent activity