← previous blocknext block →recent activity

Analyzing

Block #74,803,653

17 transactions · 14 stateful · 2026-05-15 18:16:50 UTC

Parallelism

71/100

Blocked

57%

Avg conflicts / tx

0.88

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,803,653  ·  17 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

0x0d0b2509…074d

0x3bd359…433a

10 touches
10 conflicts

0xe6455d1f…1029

0x754704…b603

10 touches
10 conflicts

0xa02838a3…bc54

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xdb0a8872…a494

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

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: Wrapped MON (WMON)

10 conflicts on slot 0x0d0b2509ae…4b074d

← previous block·next block →recent activity