← previous blocknext block →recent activity

Analyzing

Block #75,502,141

24 transactions · 21 stateful · 2026-05-19 00:07:11 UTC

Parallelism

63/100

Blocked

57%

Avg conflicts / tx

1.42

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #75,502,141  ·  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

14 touches
21 conflicts

0x5086c64a…28ba

0x34b655…2a6f

12 touches
15 conflicts

0x9e719c7a…df63

0x34b655…2a6f

10 touches
10 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

6 touches
3 conflicts

0x2796c028…023b

0x34b655…2a6f

6 touches
3 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

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