← previous blocknext block →recent activity

Analyzing

Block #74,766,641

40 transactions · 32 stateful · 2026-05-15 14:09:32 UTC

Parallelism

68/100

Blocked

66%

Avg conflicts / tx

2.08

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #74,766,641  ·  40 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

0x60f7fbaf…bd58

0x34b655…2a6f

22 touches
55 conflicts

0x0de7749d…5bef

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xa9988419…9f45

0x34b655…2a6f

8 touches
6 conflicts

0x95e5ee51…5e3e

0x34b655…2a6f

8 touches
6 conflicts

0x10814d14…cdda

0x34b655…2a6f

8 touches
6 conflicts

0x51087f5a…61f7

0x34b655…2a6f

8 touches
6 conflicts

0x46e2bb67…d8b3

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

55 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity