← previous blocknext block →recent activity

Analyzing

Block #74,351,400

13 transactions · 10 stateful · 2026-05-13 15:55:08 UTC

Parallelism

69/100

Blocked

30%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,351,400  ·  13 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x8c49c85c…ee96

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x1bde0d88…9fcf

0x34b655…2a6f

4 touches
1 conflict

0x67cfc02c…9f9a

0x34b655…2a6f

4 touches
1 conflict

0x3dbd9177…e936

0xea1b8e…c5ec

2 touches
0 conflicts

0x455b104f…3960

0xea1b8e…c5ec

2 touches
0 conflicts

0x70a23890…1244

0xea1b8e…c5ec

2 touches
0 conflicts

0xb6b74ae0…8d5e

0xea1b8e…c5ec

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 0x8c49c85c3e…afee96

← previous block·next block →recent activity