← previous blocknext block →recent activity

Analyzing

Block #74,390,018

31 transactions · 25 stateful · 2026-05-13 20:12:11 UTC

Parallelism

68/100

Blocked

64%

Avg conflicts / tx

2.06

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,390,018  ·  31 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

0x33b92274…8c6c

0xd32edf…ff58

17 touches
36 conflicts

0x1c389468…6b0e

0x34b655…2a6f

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…002a

0x1b6862…e19c

8 touches
6 conflicts

0x792299c4…16b3

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

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: 0xd32edf66…9fff58

36 conflicts on slot 0x33b92274fb…108c6c

← previous block·next block →recent activity