← previous blocknext block →recent activity

Analyzing

Block #74,204,512

22 transactions · 16 stateful · 2026-05-12 23:38:22 UTC

Parallelism

77/100

Blocked

25%

Avg conflicts / tx

0.45

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,204,512  ·  22 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

0x011fb8e3…054a

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x9e0e23b5…6910

0x34b655…2a6f

6 touches
3 conflicts

0xafd59af5…5257

0xc8689a…ee79

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0xeaa48637…ccde

0x34b655…2a6f

4 touches
1 conflict

0xeb0915f1…c150

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

10 conflicts on slot 0x011fb8e3fc…d4054a

← previous block·next block →recent activity