← previous blocknext block →recent activity

Analyzing

Block #74,190,532

42 transactions · 30 stateful · 2026-05-12 22:05:21 UTC

Parallelism

79/100

Blocked

67%

Avg conflicts / tx

1.33

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,190,532  ·  42 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x72a493d2…d0a4

0xd32edf…ff58

13 touches
21 conflicts

0xac2a0273…721b

0x34b655…2a6f

12 touches
15 conflicts

0x3b3a5945…10d0

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…001e

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002e

0x1b6862…e19c

8 touches
6 conflicts

0xc3483764…f29c

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x60f7fbaf…bd58

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

21 conflicts on slot 0x72a493d228…1cd0a4

← previous block·next block →recent activity