← previous blocknext block →recent activity

Analyzing

Block #74,762,965

12 transactions · 9 stateful · 2026-05-15 13:44:55 UTC

Parallelism

83/100

Blocked

22%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,762,965  ·  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

0xd7c02556…97f8

0x065c9d…c394

4 touches
1 conflict

0xb9bd3e4c…c842

0x065c9d…c394

4 touches
1 conflict

0xbb10fd28…a9c5

0x065c9d…c394

3 touches
1 conflict

0x7714f19b…a801

0x065c9d…c394

3 touches
1 conflict

0x19bf56f2…4f4f

0x065c9d…c394

2 touches
0 conflicts

0x443a3e47…f4a4

0x065c9d…c394

2 touches
0 conflicts

0xfcb7b8b2…ebb3

0x065c9d…c394

2 touches
0 conflicts

0x43f02fe0…f464

0x1b6862…e19c

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: 0x065c9d28…a9c394

1 conflict on slot 0xd7c02556da…6497f8

← previous block·next block →recent activity