← previous blocknext block →recent activity

Analyzing

Block #74,415,771

24 transactions · 19 stateful · 2026-05-13 23:03:37 UTC

Parallelism

63/100

Blocked

53%

Avg conflicts / tx

1.25

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,415,771  ·  24 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x1c389468…6b0e

0x34b655…2a6f

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xdef19d99…c0a9

0x34b655…2a6f

7 touches
6 conflicts

0x35b65947…44d1

0xc8689a…ee79

6 touches
3 conflicts

0x8fdebdb1…d449

0x34b655…2a6f

6 touches
3 conflicts

0x904fc3c0…00ec

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity