← previous blocknext block →recent activity

Analyzing

Block #74,920,259

34 transactions · 26 stateful · 2026-05-16 07:14:30 UTC

Parallelism

68/100

Blocked

73%

Avg conflicts / tx

2.21

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,920,259  ·  34 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

22 touches
55 conflicts

0x10f5f4d8…572e

0x34b655…2a6f

12 touches
15 conflicts

0x6ee86c0c…50c6

0x34b655…2a6f

12 touches
15 conflicts

0x7cb2f3fa…4836

0x34b655…2a6f

12 touches
15 conflicts

0xeb0915f1…c150

0x34b655…2a6f

12 touches
15 conflicts

0xafd59af5…5257

0xc8689a…ee79

12 touches
15 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

12 touches
15 conflicts

0x00000000…0002

0xab3526…fa38

12 touches
15 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

55 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity