← previous blocknext block →recent activity

Analyzing

Block #74,600,147

37 transactions · 26 stateful · 2026-05-14 19:38:02 UTC

Parallelism

86/100

Blocked

54%

Avg conflicts / tx

0.78

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,600,147  ·  37 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

0x00000000…0002

0xab3526…fa38

10 touches
10 conflicts

0x24968e6d…0132

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x816881fb…e436

0x34b655…2a6f

6 touches
3 conflicts

0x8e66c393…c9a2

0x34b655…2a6f

6 touches
3 conflicts

0xbbee74c2…567a

0x065c9d…c394

6 touches
3 conflicts

0xa92c8763…6d7f

0x34b655…2a6f

6 touches
3 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: 0xab35264b…1cfa38

10 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity