← previous blocknext block →recent activity

Analyzing

Block #74,454,621

27 transactions · 15 stateful · 2026-05-14 03:22:15 UTC

Parallelism

78/100

Blocked

60%

Avg conflicts / tx

0.93

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,454,621  ·  27 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0x38c47502…1005

0x34b655…2a6f

10 touches
10 conflicts

0x15c9b5bf…f732

0x34b655…2a6f

6 touches
3 conflicts

0x2484cc15…5afc

0x34b655…2a6f

6 touches
3 conflicts

0x2f68ee74…bf7f

0x34b655…2a6f

6 touches
3 conflicts

0x313f2565…5b00

0x34b655…2a6f

6 touches
3 conflicts

0x4118ae27…23f9

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

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity