← previous blocknext block →recent activity

Analyzing

Block #74,510,262

6 transactions · 6 stateful · 2026-05-14 09:33:14 UTC

Parallelism

50/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,510,262  ·  6 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0xd6aabe89…92f5

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0x03b4fefa…9a00

0x34b655…2a6f

2 touches
0 conflicts

0x085df2c1…305a

0x34b655…2a6f

2 touches
0 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

2 touches
0 conflicts

0x1eb0fab5…3517

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity