← previous blocknext block →recent activity

Analyzing

Block #74,765,082

33 transactions · 18 stateful · 2026-05-15 13:59:04 UTC

Parallelism

91/100

Blocked

28%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,765,082  ·  33 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

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xafd59af5…5257

0xc8689a…ee79

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0xeb0915f1…c150

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xfcb7b8b2…ebb3

0x065c9d…c394

4 touches
1 conflict

0x93a347a1…883f

0x34b655…2a6f

4 touches
1 conflict

0x8a6ce089…81c3

0x34b655…2a6f

4 touches
1 conflict

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