← previous blocknext block →recent activity

Analyzing

Block #74,920,041

41 transactions · 30 stateful · 2026-05-16 07:13:03 UTC

Parallelism

76/100

Blocked

60%

Avg conflicts / tx

1.05

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,920,041  ·  41 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

12 touches
15 conflicts

0xeb0915f1…c150

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xafd59af5…5257

0xc8689a…ee79

8 touches
6 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

8 touches
6 conflicts

0x10f5f4d8…572e

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x7cb2f3fa…4836

0x34b655…2a6f

8 touches
6 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

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity