← previous blocknext block →recent activity

Analyzing

Block #74,920,458

34 transactions · 25 stateful · 2026-05-16 07:15:50 UTC

Parallelism

62/100

Blocked

64%

Avg conflicts / tx

1.85

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #74,920,458  ·  34 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

14 touches
21 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

14 touches
21 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0x93af5ad2…45f1

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x3b265432…4129

0x34b655…2a6f

8 touches
6 conflicts

0x0380ead4…3a27

0x34b655…2a6f

8 touches
6 conflicts

0xb378025c…30cf

0x34b655…2a6f

6 touches
3 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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity