← previous blocknext block →recent activity

Analyzing

Block #74,303,371

10 transactions · 7 stateful · 2026-05-13 10:35:51 UTC

Parallelism

80/100

Blocked

14%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,303,371  ·  10 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

0xb85acbb2…d7af

0x34b655…2a6f

4 touches
1 conflict

0xbb1747e2…f78b

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x4d3e58e0…a2d7

0x34b655…2a6f

4 touches
1 conflict

0xd1a0adf6…6e55

0x54cd53…9e7d

2 touches
0 conflicts

0x08db46a3…3aee

0x6657d1…8ccc

2 touches
0 conflicts

0x0d2f989b…af4a

0x6657d1…8ccc

2 touches
0 conflicts

0x107f3f0f…3359

0x6657d1…8ccc

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 0xb85acbb2b1…b3d7af

← previous block·next block →recent activity