← previous blocknext block →recent activity

Analyzing

Block #74,510,628

12 transactions · 9 stateful · 2026-05-14 09:35:43 UTC

Parallelism

67/100

Blocked

44%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,510,628  ·  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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xd05eb970…2d89

0x065c9d…c394

5 touches
3 conflicts

0x27f979bc…f8d4

0xd32edf…ff58

5 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x3bd55803…5d4d

0x1b6862…e19c

4 touches
1 conflict

0xa980598e…ec52

0x3bd359…433a

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity