← previous blocknext block →recent activity

Analyzing

Block #74,010,262

12 transactions · 9 stateful · 2026-05-12 02:06:25 UTC

Parallelism

83/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,010,262  ·  12 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x9ea57326…329f

0x34b655…2a6f

4 touches
1 conflict

0xa15427f6…d932

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x06731366…0e9f

0x065c9d…c394

2 touches
0 conflicts

0x215c28c8…a5c6

0x065c9d…c394

2 touches
0 conflicts

0x38bcb35f…f66c

0x065c9d…c394

2 touches
0 conflicts

0x6f08361d…bda6

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 0x9ea57326ca…60329f

← previous block·next block →recent activity