← previous blocknext block →recent activity

Analyzing

Block #74,954,222

12 transactions · 11 stateful · 2026-05-16 11:01:46 UTC

Parallelism

67/100

Blocked

27%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,954,222  ·  12 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x631b4113…baa9

0x34b655…2a6f

6 touches
3 conflicts

0x97b0b2ee…4666

0x34b655…2a6f

4 touches
1 conflict

0xa92c8763…6d7f

0x34b655…2a6f

4 touches
1 conflict

0x82d3b8fd…53b4

0x754704…b603

2 touches
0 conflicts

0xfd4bd0e6…5918

0x754704…b603

2 touches
0 conflicts

0x00000000…0009

0xae0830…85fe

2 touches
0 conflicts

0xc39192d6…d4df

0xae0830…85fe

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity