← previous blocknext block →recent activity

Analyzing

Block #74,473,590

17 transactions · 9 stateful · 2026-05-14 05:28:26 UTC

Parallelism

82/100

Blocked

33%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,473,590  ·  17 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

0xadac4a86…c2bc

0x34b655…2a6f

4 touches
1 conflict

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x365d953f…8e00

0x065c9d…c394

2 touches
0 conflicts

0x485bca21…64f4

0x065c9d…c394

2 touches
0 conflicts

0xac78986d…50ad

0x065c9d…c394

2 touches
0 conflicts

0xc1e027f8…3871

0x065c9d…c394

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 0xadac4a860c…a3c2bc

← previous block·next block →recent activity