← previous blocknext block →recent activity

Analyzing

Block #74,959,663

11 transactions · 10 stateful · 2026-05-16 11:38:27 UTC

Parallelism

55/100

Blocked

40%

Avg conflicts / tx

0.45

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,959,663  ·  11 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xf8e6479f…f193

0x34b655…2a6f

4 touches
1 conflict

0x8a5efe9a…fa31

0x34b655…2a6f

4 touches
1 conflict

0x414e9446…4b59

0x34b655…2a6f

2 touches
0 conflicts

0x4f0b45b3…e2fb

0x34b655…2a6f

2 touches
0 conflicts

0x54a1467c…5bf6

0x34b655…2a6f

2 touches
0 conflicts

0x631b4113…baa9

0x34b655…2a6f

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity