← previous blocknext block →recent activity

Analyzing

Block #74,465,974

9 transactions · 9 stateful · 2026-05-14 04:37:53 UTC

Parallelism

67/100

Blocked

33%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,465,974  ·  9 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

0x079d4375…fabc

0x699abc…6a3b

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x9d88933d…81d5

0x065c9d…c394

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x86d39e4e…a3f0

0xd32edf…ff58

3 touches
1 conflict

0x144c84ff…5e9f

0x699abc…6a3b

3 touches
1 conflict

0x00000000…002c

0x1b6862…e19c

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: 0x699abc15…c86a3b

1 conflict on slot 0x079d437504…02fabc

← previous block·next block →recent activity