← previous blocknext block →recent activity

Analyzing

Block #74,423,140

12 transactions · 11 stateful · 2026-05-13 23:52:38 UTC

Parallelism

83/100

Blocked

9%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,423,140  ·  12 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

0x28c180e1…f1e2

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x62e20208…be65

0x0555e3…2b9c

2 touches
0 conflicts

0x846f2172…fd54

0x0555e3…2b9c

2 touches
0 conflicts

0x9bad8822…a28c

0x0555e3…2b9c

2 touches
0 conflicts

0xe64f78af…51a7

0x0555e3…2b9c

2 touches
0 conflicts

0xdf93ff27…3b79

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0000

0x094452…0a09

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 0x28c180e141…a4f1e2

← previous block·next block →recent activity