← previous blocknext block →recent activity

Analyzing

Block #74,499,283

9 transactions · 8 stateful · 2026-05-14 08:19:23 UTC

Parallelism

78/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,499,283  ·  9 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

0xab621973…cc16

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe181f491…f4e3

0x34b655…2a6f

4 touches
1 conflict

0x44232a83…0572

0x065c9d…c394

2 touches
0 conflicts

0x811895e0…11cc

0x065c9d…c394

2 touches
0 conflicts

0x81b8e7d1…3ec2

0x065c9d…c394

2 touches
0 conflicts

0x994b9aea…2fe9

0x065c9d…c394

2 touches
0 conflicts

0xd20ba060…474e

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 0xab621973ca…74cc16

← previous block·next block →recent activity