← previous blocknext block →recent activity

Analyzing

Block #74,648,870

7 transactions · 6 stateful · 2026-05-15 01:03:01 UTC

Parallelism

57/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,648,870  ·  7 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x19ed8762…a8b7

0x065c9d…c394

3 touches
1 conflict

0x4103e62a…c388

0x065c9d…c394

3 touches
1 conflict

0xa41e4d88…4ea0

0x065c9d…c394

3 touches
1 conflict

0xe6f24a07…c241

0x065c9d…c394

2 touches
0 conflicts

0xea1e7e75…7161

0x065c9d…c394

2 touches
0 conflicts

0xffe431af…8faa

0x065c9d…c394

2 touches
0 conflicts

0x046a928e…0012

0x2a68ba…90c5

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity