← previous blocknext block →recent activity

Analyzing

Block #74,218,478

39 transactions · 31 stateful · 2026-05-13 01:11:17 UTC

Parallelism

67/100

Blocked

68%

Avg conflicts / tx

2.08

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #74,218,478  ·  39 txs across 13 waves  ·  depth 13
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

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

0xc824469a…6425

0x34b655…2a6f

16 touches
28 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

14 touches
21 conflicts

0x20b1228b…2487

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x4ec9ff52…e6f7

0x34b655…2a6f

8 touches
6 conflicts

0x374426df…f445

0xc8689a…ee79

8 touches
6 conflicts

0x1da1c6cb…bb3f

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