← previous blocknext block →recent activity

Analyzing

Block #74,252,962

12 transactions · 9 stateful · 2026-05-13 05:00:30 UTC

Parallelism

75/100

Blocked

33%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,252,962  ·  12 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

0x7b97d40a…09ed

0x34b655…2a6f

4 touches
1 conflict

0xc3aacf13…6b3d

0x34b655…2a6f

4 touches
1 conflict

0x2f387761…308c

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xc6417de0…2191

0xc8689a…ee79

4 touches
1 conflict

0x2b693d9c…9d0e

0x065c9d…c394

2 touches
0 conflicts

0x7ecaa647…e5c1

0x065c9d…c394

2 touches
0 conflicts

0xa19ff208…79bd

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

1 conflict on slot 0x7b97d40a0c…6409ed

← previous block·next block →recent activity