← previous blocknext block →recent activity

Analyzing

Block #74,425,475

10 transactions · 9 stateful · 2026-05-14 00:08:14 UTC

Parallelism

60/100

Blocked

33%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,425,475  ·  10 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

4 touches
1 conflict

0x3b2d25d4…fb40

0x34b655…2a6f

4 touches
1 conflict

0xbad68552…e6bf

0x34b655…2a6f

4 touches
1 conflict

0x4decc0f4…164c

0x34b655…2a6f

2 touches
0 conflicts

0x5e9a6588…01d2

0x34b655…2a6f

2 touches
0 conflicts

0x85a88798…f85e

0x34b655…2a6f

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

3 conflicts on slot 0xea02471df2…601542

← previous block·next block →recent activity