← previous blocknext block →recent activity

Analyzing

Block #74,916,194

37 transactions · 31 stateful · 2026-05-16 06:47:20 UTC

Parallelism

62/100

Blocked

74%

Avg conflicts / tx

2.11

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #74,916,194  ·  37 txs across 14 waves  ·  depth 14
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

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

0xd98b3c10…67b8

0x34b655…2a6f

16 touches
28 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0x00000000…0002

0xab3526…fa38

10 touches
10 conflicts

0xea57afd0…4232

0x34b655…2a6f

10 touches
10 conflicts

0x388e001a…7e04

0x34b655…2a6f

10 touches
10 conflicts

0xd1480c90…ae09

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x388f889f…a655

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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity