← previous blocknext block →recent activity

Analyzing

Block #74,775,138

29 transactions · 22 stateful · 2026-05-15 15:06:27 UTC

Parallelism

66/100

Blocked

59%

Avg conflicts / tx

1.52

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,775,138  ·  29 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

18 touches
36 conflicts

0x8a5efe9a…fa31

0x34b655…2a6f

8 touches
6 conflicts

0x388e001a…7e04

0x34b655…2a6f

8 touches
6 conflicts

0x37cfaf01…4a46

0x34b655…2a6f

6 touches
3 conflicts

0x15007455…ed03

0x34b655…2a6f

4 touches
1 conflict

0x46e2bb67…d8b3

0x34b655…2a6f

4 touches
1 conflict

0x55b6a001…1e7a

0x34b655…2a6f

4 touches
1 conflict

0x5dc14a96…6816

0x34b655…2a6f

4 touches
1 conflict

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

36 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity