← previous blocknext block →recent activity

Analyzing

Block #74,356,147

14 transactions · 13 stateful · 2026-05-13 16:26:45 UTC

Parallelism

79/100

Blocked

31%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,356,147  ·  14 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

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

6 touches
3 conflicts

0xa472d565…9fe4

0x3bd359…433a

6 touches
3 conflicts

0x9e719c7a…df63

0x34b655…2a6f

5 touches
3 conflicts

0x00000000…0001

0x75c3ab…4f0d

4 touches
1 conflict

0x85a88798…f85e

0x34b655…2a6f

4 touches
1 conflict

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 0xf3d10975b0…050d07

← previous block·next block →recent activity