← previous blocknext block →recent activity

Analyzing

Block #74,773,232

18 transactions · 14 stateful · 2026-05-15 14:53:41 UTC

Parallelism

89/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,773,232  ·  18 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x631b4113…baa9

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x8fa7a69c…8fd7

0x2f6a6c…7777

2 touches
0 conflicts

0xb3f28385…15a5

0x2f6a6c…7777

2 touches
0 conflicts

0x0eac6378…36f4

0x34b655…2a6f

2 touches
0 conflicts

0x150af51d…9c42

0x34b655…2a6f

2 touches
0 conflicts

0x8aa1941d…2988

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0x631b41138f…31baa9

← previous block·next block →recent activity