← previous blocknext block →recent activity

Analyzing

Block #74,351,683

35 transactions · 25 stateful · 2026-05-13 15:57:01 UTC

Parallelism

71/100

Blocked

64%

Avg conflicts / tx

1.83

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,351,683  ·  35 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

20 touches
45 conflicts

0x0d622e34…0000

0x681e90…ae09

10 touches
10 conflicts

0xc38a1e34…37c3

0x34b655…2a6f

8 touches
6 conflicts

0xafd59af5…5257

0xc8689a…ee79

8 touches
6 conflicts

0xeb0915f1…c150

0x34b655…2a6f

8 touches
6 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

8 touches
6 conflicts

0x10f5f4d8…572e

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

45 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity