← previous blocknext block →recent activity

Analyzing

Block #74,562,831

11 transactions · 8 stateful · 2026-05-14 15:27:58 UTC

Parallelism

82/100

Blocked

13%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,562,831  ·  11 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

0xde1a0ee7…c75b

0x34b655…2a6f

4 touches
1 conflict

0xa6464996…3af9

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x1348a4c0…8d18

0x34b655…2a6f

2 touches
0 conflicts

0x1348a4c0…8d19

0x34b655…2a6f

2 touches
0 conflicts

0x1e9bb30c…e78e

0x34b655…2a6f

2 touches
0 conflicts

0x60a42a5e…9da2

0x34b655…2a6f

2 touches
0 conflicts

0x71e4ffd1…9beb

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 0xde1a0ee72c…10c75b

← previous block·next block →recent activity