← previous blocknext block →recent activity

Analyzing

Block #74,485,468

25 transactions · 21 stateful · 2026-05-14 06:47:31 UTC

Parallelism

72/100

Blocked

57%

Avg conflicts / tx

1.48

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,485,468  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x60f7fbaf…bd58

0x34b655…2a6f

14 touches
21 conflicts

0x00000000…0002

0xab3526…fa38

12 touches
15 conflicts

0xafd59af5…5257

0xc8689a…ee79

6 touches
3 conflicts

0x10f5f4d8…572e

0x34b655…2a6f

6 touches
3 conflicts

0x3906f425…1048

0x34b655…2a6f

6 touches
3 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

6 touches
3 conflicts

0x7cb2f3fa…4836

0x34b655…2a6f

6 touches
3 conflicts

0xa21e8abe…a7f1

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: 0x34b6552d…112a6f

21 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity