← previous blocknext block →recent activity

Analyzing

Block #74,763,055

13 transactions · 13 stateful · 2026-05-15 13:45:32 UTC

Parallelism

62/100

Blocked

38%

Avg conflicts / tx

0.46

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,763,055  ·  13 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

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x388e001a…7e04

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf853eb8e…4027

0x34b655…2a6f

4 touches
1 conflict

0x955ba814…f912

0x065c9d…c394

2 touches
0 conflicts

0xce112cd7…1263

0x065c9d…c394

2 touches
0 conflicts

0xd6012273…f9a3

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

3 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity