← previous blocknext block →recent activity

Analyzing

Block #74,334,145

32 transactions · 30 stateful · 2026-05-13 14:00:28 UTC

Parallelism

40/100

Blocked

70%

Avg conflicts / tx

5.69

Longest chain

19 deep

Execution timeline

did this block parallelize well?

view

block #74,334,145  ·  32 txs across 19 waves  ·  depth 19
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

wave w13

wave w14

wave w15

wave w16

wave w17

wave w18

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

0xc6417de0…2191

0xc8689a…ee79

38 touches
171 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

32 touches
120 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

26 touches
78 conflicts

0x908d4442…2c4b

0x34b655…2a6f

24 touches
66 conflicts

0x9be2b99a…a959

0x34b655…2a6f

22 touches
55 conflicts

0x99f080dc…58c1

0x34b655…2a6f

20 touches
45 conflicts

0xa9d9912c…75a7

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

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: 0xc8689a47…62ee79

171 conflicts on slot 0xc6417de023…802191

← previous block·next block →recent activity